Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

[Akihiro Motoki]

Hi Cathy and folks interested in SFC and classifers!

Can't we use a different room like Salon D?
Salon C is a lunch room and at that time there are no sessions in other rooms.
It would be great if we can use Salon D or E (after looking at the
first day's session)
I think we can gather more easily and concentrate the discussion if we
use some different space.
Thought?

Akihiro

2016-04-22 17:30 GMT-05:00 Cathy Zhang :
> Hi Everyone,
>
>
>
> As we discussed in our project meeting, we should have a f2f meeting during
> the summit.
>
> let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday.
>
> Since Salon C is a big room, I will put a sign “Networking-SFC Project
> Meet-Up” on the table.
>
>
>
> Thanks,
>
> Cathy
>
>

__
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][Monasca] Traffic counters at Layer 3

[Akihiro Motoki]

Neutron already supports L3 router with network namespaces which send
notifications, as Armando mentioned.
Ceilometer can consume these notification and I think monisca can do
similar things.
I believe you can collect enough information for neutron ovs implementation.

2016-04-25 13:20 GMT-05:00 Rubab Syed :
> Hi folks,
>
> I'm writing a plugin for Monasca to monitor traffic at layer 3. My Neutron
> backend is OVS and I'm using iptables of network namespaces for getting
> traffic counters. Would the following rules in router namespace cover all
> the traffic at layer 3 per router per tenant?
>
> - Chain MONASCA-INPUT in filter table
>- src: anywhere dest: gateway port IP   // north-south traffic for
> SNATed and FIPs
>
> - Chain MONASCA-FORWARD in filter table
>   - src: anywhere   dest: anywhere  // east-west traffic
> inter-network and intra-network
>
> - Chain MONASCA-OUTPUT in filter table
>   - src: gateway port dest: anywhere  // north-south traffic from
> VMs to public network
>
>
> Would these be sufficient or am I missing something?
>
> Thanks!
>
> Rubab
>
> __
> 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] Social at the summit

[reedip banerjee]

+2 :p

On Tue, Apr 26, 2016 at 8:39 AM, Vasudevan, Swaminathan (PNB Roseville) <
swaminathan.vasude...@hpe.com> wrote:

> Count me in. +1.
>
> Thanks
> Swami
>
> -Original Message-
> From: Kyle Mestery [mailto:mest...@mestery.com]
> Sent: Monday, April 25, 2016 11:07 AM
> To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [neutron] Social at the summit
>
> OK, there is enough interest, I'll find a place on 6th Street for us and
> get a reservation for Thursday around 7 or so.
>
> Thanks folks!
>
> On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> > +1 :)
> >
> > Han Zhou
> > Irc: zhouhan
> >
> >
> > On Monday, April 25, 2016, Korzeniewski, Artur
> >  wrote:
> >>
> >> Sign me up :)
> >>
> >> Artur
> >> IRC: korzen
> >>
> >> -Original Message-
> >> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
> >> Sent: Monday, April 25, 2016 7:19 PM
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> 
> >> Subject: Re: [openstack-dev] [neutron] Social at the summit
> >>
> >> Count me in!
> >> Will be good to meet all you guys!
> >>
> >> Darek (dasm) Smigiel
> >>
> >> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
> >> >  wrote:
> >> >
> >> >
> >> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka
> >> >> 
> >> >> wrote:
> >> >>
> >> >> WAT???
> >> >>
> >> >> It was never supposed to be core only. Everyone is welcome!
> >> >
> >> > +2
> >> >
> >> > irony intended.
> >> >
> >> > Socials are not controlled by gerrit ACLs.  :-)
> >> >
> >> > doug
> >> >
> >> >>
> >> >> Sent from my iPhone
> >> >>
> >> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
> >> >>> wrote:
> >> >>>
> >> >>> Would you extend it to ex-cores?
> >> >>>
> >> >>> Edgar
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
> >> 
> >>  Ihar, Henry and I were talking and we thought Thursday night
> >>  makes sense for a Neutron social in Austin. If others agree,
> >>  reply on this thread and we'll find a place.
> >> 
> >>  Thanks!
> >>  Kyle
> >> 
> >>  
> >>  ___ ___ 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-de
> >>  v
> >> >>> _
> >> >>> ___ __ 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 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 

Re: [openstack-dev] [OpenStack][Neutron][Monasca] Traffic counters at Layer 3

[Armando M.]

On 25 April 2016 at 11:20, Rubab Syed  wrote:

> Hi folks,
>
> I'm writing a plugin for Monasca to monitor traffic at layer 3. My Neutron
> backend is OVS and I'm using iptables of network namespaces for getting
> traffic counters. Would the following rules in router namespace cover all
> the traffic at layer 3 per router per tenant?
>
> - Chain MONASCA-INPUT in filter table
>- src: anywhere dest: gateway port IP   // north-south traffic for
> SNATed and FIPs
>
> - Chain MONASCA-FORWARD in filter table
>   - src: anywhere   dest: anywhere  // east-west traffic
> inter-network and intra-network
>
> - Chain MONASCA-OUTPUT in filter table
>   - src: gateway port dest: anywhere  // north-south traffic from
> VMs to public network
>
>
> Would these be sufficient or am I missing something?
>

Have you looked at the iptables driver already available in Neutron [1]?
That should give enough pointers.

[1]
https://github.com/openstack/neutron/blob/master/neutron/services/metering/drivers/iptables/iptables_driver.py


>
> Thanks!
>
> Rubab
>
> __
> 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] [TC][tricircle] ask help from TC and other guru in the OpenStack community

[joehuang]

Hi, TCs and guru,



If tricircle planned to apply being TC approved big tent project, would someone 
help to guide our project?



I would like to have one  virtual design summit for Tricircle on UTC 2:00am on 
Friday ( Beijing Time 10:00am Apr. 29), ( Austin time: 9:00pm Apr.28 )



Best Regards

Chaoyi Huang ( joehuang )




From: joehuang
Sent: 26 April 2016 11:40
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev][tricircle] virtual design summit for Newton


Hello,



Most of our team members in Tricircle are not able to attend the OpenStack 
Austin summit, so we have to have a virtual design summit:



One etherpad is opened for the topics to be discussed for the virtual Newton 
design summit, please list the topics you want to discuss in the etherpad:



https://etherpad.openstack.org/p/TricircleNeutonDesignSummit



The date and time to have this virtual design summit will be at UTC 2:00am on 
Friday ( Beijing Time 10:00am) Apr. 29. ( Austin time: 9:00pm Apr.28 )



To make Tricircle fully follow OpenStack projects open source development, I 
think we need to apply Tricircle as TC approved big tent project in Newton, so 
this is also one important topic to be discussed.



Any suggestion are welcome.



Best Regards

Chaoyi Huang ( joehuang )


From: joehuang
Sent: 19 April 2016 16:33
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle]weekly meeting of Apr. 19

This week we will discuss the object operation not implemented.

IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every 
Wednesday starting from UTC 13:00.

Agenda:
# object operation not implemented
# tempest test
# Reliable aync. Job – items left
# Link: https://etherpad.openstack.org/p/TricircleToDo

If you  have other topics to be discussed in the weekly meeting, please reply 
the mail.

Best Regards
Chaoyi Huang ( Joe Huang )

__
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] [tricircle] virtual design summit for Newton

[joehuang]

Hello,



Most of our team members in Tricircle are not able to attend the OpenStack 
Austin summit, so we have to have a virtual design summit:



One etherpad is opened for the topics to be discussed for the Newton design 
summit, please list the topics you want to discuss in the etherpad:



https://etherpad.openstack.org/p/TricircleNeutonDesignSummit



The date and time to have this virtual design summit will be at UTC 2:00am on 
Friday ( Beijing Time 10:00am) Apr. 29. ( Austin time: 9:00pm Apr.28 )



To make Tricircle fully follow OpenStack projects open source development, I 
think we need to apply Tricircle as TC approved big tent project in Newton, so 
this is also one important topic to be discussed.



Any suggestion are welcome.



Best Regards

Chaoyi Huang ( joehuang )


From: joehuang
Sent: 19 April 2016 16:33
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [tricircle]weekly meeting of Apr. 19

This week we will discuss the object operation not implemented.

IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every 
Wednesday starting from UTC 13:00.

Agenda:
# object operation not implemented
# tempest test
# Reliable aync. Job – items left
# Link: https://etherpad.openstack.org/p/TricircleToDo

If you  have other topics to be discussed in the weekly meeting, please reply 
the mail.

Best Regards
Chaoyi Huang ( Joe Huang )

__
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] Social at the summit

[Vasudevan, Swaminathan (PNB Roseville)]

Count me in. +1.

Thanks
Swami

-Original Message-
From: Kyle Mestery [mailto:mest...@mestery.com] 
Sent: Monday, April 25, 2016 11:07 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] Social at the summit

OK, there is enough interest, I'll find a place on 6th Street for us and get a 
reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> +1 :)
>
> Han Zhou
> Irc: zhouhan
>
>
> On Monday, April 25, 2016, Korzeniewski, Artur 
>  wrote:
>>
>> Sign me up :)
>>
>> Artur
>> IRC: korzen
>>
>> -Original Message-
>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> Sent: Monday, April 25, 2016 7:19 PM
>> To: OpenStack Development Mailing List (not for usage questions) 
>> 
>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>
>> Count me in!
>> Will be good to meet all you guys!
>>
>> Darek (dasm) Smigiel
>>
>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley 
>> >  wrote:
>> >
>> >
>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> 
>> >> wrote:
>> >>
>> >> WAT???
>> >>
>> >> It was never supposed to be core only. Everyone is welcome!
>> >
>> > +2
>> >
>> > irony intended.
>> >
>> > Socials are not controlled by gerrit ACLs.  :-)
>> >
>> > doug
>> >
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >>> wrote:
>> >>>
>> >>> Would you extend it to ex-cores?
>> >>>
>> >>> Edgar
>> >>>
>> >>>
>> >>>
>> >>>
>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>>  Ihar, Henry and I were talking and we thought Thursday night 
>>  makes sense for a Neutron social in Austin. If others agree, 
>>  reply on this thread and we'll find a place.
>> 
>>  Thanks!
>>  Kyle
>> 
>>  
>>  ___ ___ 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-de
>>  v
>> >>> _
>> >>> ___ __ 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 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

Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project f2f2 meet-up place and time

[Cathy Zhang]

Hi Stephen,

Yes, I will take notes on the etherpad.

Thanks,
Cathy

From: Stephen Wong [mailto:stephen.kf.w...@gmail.com]
Sent: Monday, April 25, 2016 3:05 PM
To: Cathy Zhang
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] [networking-sfc] Network-sfc project 
f2f2 meet-up place and time

Hi,

Unfortunately I will miss this f2f meeting since I won't arrive until late 
evening on Tuesday. But I did update the etherpad LouisF posted [1] (during the 
last IRC meeting) with some topics of interest. If any of them happens to be 
discussed during Tuesday's meetup, please update the etherpad accordingly. 
Thanks!

Actually, in general, please take notes in the etherpad so we can review as 
topics of interest (and corresponding discussion points) for development 
planning for the next cycle.

Thanks,
- Stephen

[1]  https://etherpad.openstack.org/p/networking-sfc-austin-summit-meeting

On Fri, Apr 22, 2016 at 3:30 PM, Cathy Zhang 
> wrote:
Hi Everyone,

As we discussed in our project meeting, we should have a f2f meeting during the 
summit.
let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday.
Since Salon C is a big room, I will put a sign “Networking-SFC Project Meet-Up” 
on the table.

Thanks,
Cathy


__
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] Social at the summit

[Cathy Zhang]

Hi Kyle,

Thanks for this. Count me in. 

Cathy

-Original Message-
From: Kyle Mestery [mailto:mest...@mestery.com] 
Sent: Monday, April 25, 2016 11:07 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron] Social at the summit

OK, there is enough interest, I'll find a place on 6th Street for us and get a 
reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> +1 :)
>
> Han Zhou
> Irc: zhouhan
>
>
> On Monday, April 25, 2016, Korzeniewski, Artur 
>  wrote:
>>
>> Sign me up :)
>>
>> Artur
>> IRC: korzen
>>
>> -Original Message-
>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> Sent: Monday, April 25, 2016 7:19 PM
>> To: OpenStack Development Mailing List (not for usage questions) 
>> 
>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>
>> Count me in!
>> Will be good to meet all you guys!
>>
>> Darek (dasm) Smigiel
>>
>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley 
>> >  wrote:
>> >
>> >
>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> 
>> >> wrote:
>> >>
>> >> WAT???
>> >>
>> >> It was never supposed to be core only. Everyone is welcome!
>> >
>> > +2
>> >
>> > irony intended.
>> >
>> > Socials are not controlled by gerrit ACLs.  :-)
>> >
>> > doug
>> >
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >>> wrote:
>> >>>
>> >>> Would you extend it to ex-cores?
>> >>>
>> >>> Edgar
>> >>>
>> >>>
>> >>>
>> >>>
>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>>  Ihar, Henry and I were talking and we thought Thursday night 
>>  makes sense for a Neutron social in Austin. If others agree, 
>>  reply on this thread and we'll find a place.
>> 
>>  Thanks!
>>  Kyle
>> 
>>  
>>  ___ ___ 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-de
>>  v
>> >>> _
>> >>> ___ __ 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 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

Re: [openstack-dev] [heat]informal meetup during summit

[Steve Baker]

We are now at Terry black's BBQ now for anyone who wants to join usThanks for 
organising Rico! See you when you get there.

- ZB


On 22/04/16 20:01, Rico Lin wrote:
> Let's settle down on with
>
> A meet up on Monday night 7:00pm
> At continentalclub
> 
> address : 1315 S Congress Ave
> Austin, TX 78704 http://continentalclub.com
> 
> And
> Friday morning 10:00 venue:TBD
>
> Is the time and venue find with everyone?
>
> Everyone are welcome :)
> Feel free to let me know if you're coming, just for easy pre-booking
> purpose:)
>
> On Apr 22, 2016 12:13 AM, "Zane Bitter"  > wrote:
>
> On 20/04/16 13:00, Rico Lin wrote:
>
> Hi team
> Let plan for more informal meetup(relax) time! Let all heaters
> and any
> other projects can have fun and chance for technical discussions
> together.
>
> After discuss in meeting, we will have a pre-meetup-meetup on Friday
> morning to have a cup of cafe or some food. Would like to ask if
> anyone
> knows any nice place for this meetup?:)
>
>
> According to
> https://www.openstack.org/summit/austin-2016/guide-to-austin/ if we
> line up at Franklin's at 7am then we can be eating barbeque by 11
> and still make it back in time for the afternoon meetup :))
>
> Also open for other chance for all can go out for a nice dinner and
> beer. Right now seems maybe Monday or Friday night could be the best
> candidate for this wonderful task, what all think about this? :)
>
>
> +1. I'll be around on Friday, but I imagine a few people will be
> leaving so Monday is probably better.
>
> cheers,
> Zane.
>
> __
> 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

Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic

[Jeffrey Zhang]

+1

On Tue, Apr 26, 2016 at 6:00 AM, Ryan Hallisey  wrote:

> +1
>
> - Original Message -
> From: "Angus Salkeld" 
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Sent: Sunday, April 24, 2016 11:01:38 AM
> Subject: Re: [openstack-dev] [kolla][vote] Place kolla-mesos in
> openstack-attic
>
>
>
> +1
> On Sat, 23 Apr 2016 3:08 am Michał Rostecki < michal.roste...@gmail.com >
> wrote:
>
>
> +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
>
> __
> 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,
Jeffrey Zhang
Blog: http://xcodest.me
__
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] Devstack liberty with keystone v3

[ZhiQiang Fan]

what you need is this patch: https://review.openstack.org/#/c/307574/

after install finished, to use admin:demo account and v3 API, run ``source
openrc -k3 admin``, then it is done.

Cheers!

On Tue, Apr 26, 2016 at 7:10 AM, kiran vemuri UH  wrote:

> Hello All,
>
> I recently got started with OpenStack with a goal of bringing up a multi
> region setup i.e., 2 regions using the same keystone service.
>
> I started with devstack liberty stable release by following the
> documentation available at:
> http://docs.openstack.org/developer/devstack/#configuration
>
> I am able to bring up the liberty but it boots with keystone v2 as
> default. Could anyone please point me to the documentation on how to enable
> keystone v3?
>
> I tried making changes to local.conf file with the following parameters.
>
> ENABLE_IDENTITY_V2=False
> IDENTITY_API_VERSION=3
> OS_IDENTITY_API_VERSION=3
> DEFAULT_DOMAIN=default
>
> but, everytime I do unstack and stack, it results in error similar to this
> https://bugs.launchpad.net/devstack/+bug/1490950
>
> I also tried solutions listed in the above bug.. but nothing helped.
>
> Could anyone help me out with this?
>
> Thanks,
> Kiran Vemuri
>
> *kiran vemuri*
> www.kiranvemuri.info
> Tel: (832)-701-8281
> kkvem...@uh.edu
>
> __
> 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] Block Device Mapping is Invalid

[Nathan Stratton]

I just upgraded to RDO Kilo and no longer can boot volumes. I never see
anything hit cinder, so I think the issue is inside of nova. I have been
banging my head on this one all day, would love any help anyone can provide.

[root@openstack nova(keystone)]# nova --debug boot --flavor 2 --boot-volume
5c69b767-5c35-4acf-984f-5a6c3b3ddac8 dns2 --nic
net-id=b2324538-26ee-4d06-bccd-0ef2f6778f6b,v4-fixed-ip=10.71.0.130 --nic
net-id=38353702-811a-42a0-9d90-10a6019d22a7,v4-fixed-ip=50.205.128.46
--availability-zone nova:virt05b.broadsoftlabs.net
DEBUG (session:195) REQ: curl -g -i -X GET http://10.71.0.218:5000/v2.0/ -H
"Accept: application/json" -H "User-Agent: python-keystoneclient"
INFO (connectionpool:213) Starting new HTTP connection (1): 10.71.0.218
DEBUG (connectionpool:393) "GET /v2.0/ HTTP/1.1" 200 337
DEBUG (session:224) RESP: [200] Content-Length: 337 Vary: X-Auth-Token
Connection: keep-alive Date: Mon, 25 Apr 2016 23:47:45 GMT Content-Type:
application/json X-Openstack-Request-Id:
req-ff89e645-514c-4c13-b2cb-4f383d93d4ce
RESP BODY: {"version": {"status": "stable", "updated":
"2014-04-17T00:00:00Z", "media-types": [{"base": "application/json",
"type": "application/vnd.openstack.identity-v2.0+json"}], "id": "v2.0",
"links": [{"href": "http://10.71.0.218:5000/v2.0/;, "rel": "self"},
{"href": "http://docs.openstack.org/;, "type": "text/html", "rel":
"describedby"}]}}

DEBUG (v2:76) Making authentication request to
http://10.71.0.218:5000/v2.0/tokens
DEBUG (connectionpool:393) "POST /v2.0/tokens HTTP/1.1" 200 3070
DEBUG (session:195) REQ: curl -g -i -X GET
http://10.71.0.218:8774/v2/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2 -H
"User-Agent: python-novaclient" -H "Accept: application/json" -H
"X-Auth-Token: {SHA1}5804468e0111677dc7e4165fecfa44f4c9e88994"
INFO (connectionpool:213) Starting new HTTP connection (1): 10.71.0.218
DEBUG (connectionpool:393) "GET
/v2/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2 HTTP/1.1" 200 423
DEBUG (session:224) RESP: [200] Date: Mon, 25 Apr 2016 23:47:46 GMT
Connection: keep-alive Content-Type: application/json Content-Length: 423
X-Compute-Request-Id: req-4bf327b3-9b03-4437-bd18-3e799b6d69f0
RESP BODY: {"flavor": {"name": "m1.small", "links": [{"href": "
http://10.71.0.218:8774/v2/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2;,
"rel": "self"}, {"href": "
http://10.71.0.218:8774/0ebcdedac0a3480ca81050bfedd97cf1/flavors/2;, "rel":
"bookmark"}], "ram": 2048, "OS-FLV-DISABLED:disabled": false, "vcpus": 2,
"swap": "", "os-flavor-access:is_public": true, "rxtx_factor": 1.0,
"OS-FLV-EXT-DATA:ephemeral": 0, "disk": 32, "id": "2"}}

DEBUG (session:195) REQ: curl -g -i -X POST
http://10.71.0.218:8774/v2/0ebcdedac0a3480ca81050bfedd97cf1/os-volumes_boot
-H "User-Agent: python-novaclient" -H "Content-Type: application/json" -H
"Accept: application/json" -H "X-Auth-Token:
{SHA1}5804468e0111677dc7e4165fecfa44f4c9e88994" -d '{"server": {"name":
"dns2", "imageRef": "", "availability_zone": "nova:virt05b.broadsoftlabs.net",
"block_device_mapping_v2": [{"source_type": "volume",
"delete_on_termination": false, "boot_index": 0, "uuid":
"5c69b767-5c35-4acf-984f-5a6c3b3ddac8", "destination_type": "volume"}],
"flavorRef": "2", "max_count": 1, "min_count": 1, "networks": [{"fixed_ip":
"10.71.0.130", "uuid": "b2324538-26ee-4d06-bccd-0ef2f6778f6b"},
{"fixed_ip": "50.205.128.46", "uuid":
"38353702-811a-42a0-9d90-10a6019d22a7"}]}}'
DEBUG (connectionpool:393) "POST
/v2/0ebcdedac0a3480ca81050bfedd97cf1/os-volumes_boot HTTP/1.1" 400 135
DEBUG (session:224) RESP:
DEBUG (shell:914) Block Device Mapping is Invalid: failed to get volume
5c69b767-5c35-4acf-984f-5a6c3b3ddac8. (HTTP 400) (Request-ID:
req-a7974c64-fbd6-49de-a34b-ea2e3672cd67)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 911, in
main
OpenStackComputeShell().main(argv)
  File "/usr/lib/python2.7/site-packages/novaclient/shell.py", line 838, in
main
args.func(self.cs, args)
  File "/usr/lib/python2.7/site-packages/novaclient/v2/shell.py", line 500,
in do_boot
server = cs.servers.create(*boot_args, **boot_kwargs)
  File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line
900, in create
**boot_kwargs)
  File "/usr/lib/python2.7/site-packages/novaclient/v2/servers.py", line
523, in _boot
return_raw=return_raw, **kwargs)
  File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 161, in
_create
_resp, body = self.api.client.post(url, body=body)
  File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line
176, in post
return self.request(url, 'POST', **kwargs)
  File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 96, in
request
raise exceptions.from_response(resp, body, url, method)
BadRequest: Block Device Mapping is Invalid: failed to get volume
5c69b767-5c35-4acf-984f-5a6c3b3ddac8. (HTTP 400) (Request-ID:
req-a7974c64-fbd6-49de-a34b-ea2e3672cd67)
ERROR (BadRequest): Block Device Mapping is Invalid: failed to get volume

Re: [openstack-dev] Devstack liberty with keystone v3

[Perry, Sean]

The trick is to let devstack install and then switch openrc to 
IDENTITY_API_VERSION=3. Both v2 and v3 endpoints are created already. The tools 
just need to be told to use them.


From: kiran vemuri UH [kkvem...@uh.edu]
Sent: Monday, April 25, 2016 4:10 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] Devstack liberty with keystone v3

Hello All,

I recently got started with OpenStack with a goal of bringing up a multi region 
setup i.e., 2 regions using the same keystone service.

I started with devstack liberty stable release by following the documentation 
available at: http://docs.openstack.org/developer/devstack/#configuration

I am able to bring up the liberty but it boots with keystone v2 as default. 
Could anyone please point me to the documentation on how to enable keystone v3?

I tried making changes to local.conf file with the following parameters.

ENABLE_IDENTITY_V2=False
IDENTITY_API_VERSION=3
OS_IDENTITY_API_VERSION=3
DEFAULT_DOMAIN=default

but, everytime I do unstack and stack, it results in error similar to this 
https://bugs.launchpad.net/devstack/+bug/1490950

I also tried solutions listed in the above bug.. but nothing helped.

Could anyone help me out with this?

Thanks,
Kiran Vemuri

kiran vemuri
www.kiranvemuri.info
Tel: (832)-701-8281
kkvem...@uh.edu

__
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] Devstack liberty with keystone v3

[kiran vemuri UH]

Hello All,

I recently got started with OpenStack with a goal of bringing up a multi
region setup i.e., 2 regions using the same keystone service.

I started with devstack liberty stable release by following the
documentation available at:
http://docs.openstack.org/developer/devstack/#configuration

I am able to bring up the liberty but it boots with keystone v2 as default.
Could anyone please point me to the documentation on how to enable keystone
v3?

I tried making changes to local.conf file with the following parameters.

ENABLE_IDENTITY_V2=False
IDENTITY_API_VERSION=3
OS_IDENTITY_API_VERSION=3
DEFAULT_DOMAIN=default

but, everytime I do unstack and stack, it results in error similar to this
https://bugs.launchpad.net/devstack/+bug/1490950

I also tried solutions listed in the above bug.. but nothing helped.

Could anyone help me out with this?

Thanks,
Kiran Vemuri

*kiran vemuri*
www.kiranvemuri.info
Tel: (832)-701-8281
kkvem...@uh.edu
__
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] Social at the summit

[Paul Michali]

+1

On Mon, Apr 25, 2016, 5:32 PM Armando M.  wrote:

> On 25 April 2016 at 10:01, Ihar Hrachyshka  wrote:
>
>> WAT???
>>
>> It was never supposed to be core only. Everyone is welcome!
>>
>
> In fact this should be cross-posted the other openstack ML too.
>
>
>> Sent from my iPhone
>>
>> > On 25 Apr 2016, at 11:56, Edgar Magana 
>> wrote:
>> >
>> > Would you extend it to ex-cores?
>> >
>> > Edgar
>> >
>> >
>> >
>> >
>> >> On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> >>
>> >> Ihar, Henry and I were talking and we thought Thursday night makes
>> sense for a Neutron social in Austin. If others agree, reply on this thread
>> and we'll find a place.
>> >>
>> >> Thanks!
>> >> Kyle
>> >>
>> >>
>> __
>> >> 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 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] Social at the summit

[Armando M.]

On 25 April 2016 at 10:01, Ihar Hrachyshka  wrote:

> WAT???
>
> It was never supposed to be core only. Everyone is welcome!
>

In fact this should be cross-posted the other openstack ML too.


> Sent from my iPhone
>
> > On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
> >
> > Would you extend it to ex-cores?
> >
> > Edgar
> >
> >
> >
> >
> >> On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
> >>
> >> Ihar, Henry and I were talking and we thought Thursday night makes
> sense for a Neutron social in Austin. If others agree, reply on this thread
> and we'll find a place.
> >>
> >> Thanks!
> >> Kyle
> >>
> >>
> __
> >> 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

Re: [openstack-dev] [neutron] Social at the summit

[John Schwarz]

+1
On 25 Apr 2016 16:48, "Carl Baldwin"  wrote:

> +1
> On Apr 25, 2016 10:57 AM, "Kyle Mestery"  wrote:
>
>> Ihar, Henry and I were talking and we thought Thursday night makes sense
>> for a Neutron social in Austin. If others agree, reply on this thread and
>> we'll find a place.
>>
>> Thanks!
>> Kyle
>>
>> __
>> 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-sfc] Network-sfc project f2f2 meet-up place and time

[Stephen Wong]

Hi,

Unfortunately I will miss this f2f meeting since I won't arrive until
late evening on Tuesday. But I did update the etherpad LouisF posted [1]
(during the last IRC meeting) with some topics of interest. If any of them
happens to be discussed during Tuesday's meetup, please update the etherpad
accordingly. Thanks!

Actually, in general, please take notes in the etherpad so we can
review as topics of interest (and corresponding discussion points) for
development planning for the next cycle.

Thanks,
- Stephen

[1]  https://etherpad.openstack.org/p/networking-sfc-austin-summit-meeting

On Fri, Apr 22, 2016 at 3:30 PM, Cathy Zhang 
wrote:

> Hi Everyone,
>
>
>
> As we discussed in our project meeting, we should have a f2f meeting
> during the summit.
>
> let’s meet at "Salon C" for lunch from 12:30pm~1:50pm on Tuesday.
>
> Since Salon C is a big room, I will put a sign “Networking-SFC Project
> Meet-Up” on the table.
>
>
>
> Thanks,
>
> Cathy
>
>
>
__
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][vote] Place kolla-mesos in openstack-attic

[Ryan Hallisey]

+1

- Original Message -
From: "Angus Salkeld" 
To: "OpenStack Development Mailing List (not for usage questions)" 

Sent: Sunday, April 24, 2016 11:01:38 AM
Subject: Re: [openstack-dev] [kolla][vote] Place kolla-mesos in openstack-attic



+1 
On Sat, 23 Apr 2016 3:08 am Michał Rostecki < michal.roste...@gmail.com > 
wrote: 


+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 

__
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] Social at the summit

[Carl Baldwin]

+1
On Apr 25, 2016 10:57 AM, "Kyle Mestery"  wrote:

> Ihar, Henry and I were talking and we thought Thursday night makes sense
> for a Neutron social in Austin. If others agree, reply on this thread and
> we'll find a place.
>
> Thanks!
> Kyle
>
> __
> 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] Social at the summit

[John McDowall]

Kyle,

If it is open to all would like to join too.

Regards

John
__
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] More on the topic of DELIMITER, the Quota Management Library proposal

[Duncan Thomas]

On 23 Apr 2016 14:26, "Jay Pipes"  wrote:

> On 04/23/2016 03:18 PM, Mike Perez wrote:

>> How about extending a volume? A volume is a resource and can be extended
in
>> Cinder today.
>
>
> Yep, understood :) I recognize some resource amounts can be modified for
some resource classes. How about *shrinking* a volume. Is that supported?

Currently, no, but saying we can never implement it because the quota
library will never support it is the tail wagging the dog in a big way.
__
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] Social at the summit

[Michael Micucci]

I'd love to join as well!

On 4/25/2016 3:56 PM, Brian Haley wrote:

+1

On 4/25/16 1:07 PM, Kyle Mestery wrote:

OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:

+1 :)

Han Zhou
Irc: zhouhan


On Monday, April 25, 2016, Korzeniewski, Artur
 wrote:


Sign me up :)

Artur
IRC: korzen

-Original Message-
From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
Sent: Monday, April 25, 2016 7:19 PM
To: OpenStack Development Mailing List (not for usage questions)

Subject: Re: [openstack-dev] [neutron] Social at the summit

Count me in!
Will be good to meet all you guys!

Darek (dasm) Smigiel


On Apr 25, 2016, at 12:13 PM, Doug Wiegley
 wrote:



On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
wrote:

WAT???

It was never supposed to be core only. Everyone is welcome!


+2

irony intended.

Socials are not controlled by gerrit ACLs.  :-)

doug



Sent from my iPhone


On 25 Apr 2016, at 11:56, Edgar Magana 
wrote:

Would you extend it to ex-cores?

Edgar





On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:

Ihar, Henry and I were talking and we thought Thursday night makes
sense for a Neutron social in Austin. If others agree, reply on 
this thread

and we'll find a place.

Thanks!
Kyle

___ 


___ 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 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 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] Social at the summit

[Brian Haley]

+1

On 4/25/16 1:07 PM, Kyle Mestery wrote:

OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:

+1 :)

Han Zhou
Irc: zhouhan


On Monday, April 25, 2016, Korzeniewski, Artur
 wrote:


Sign me up :)

Artur
IRC: korzen

-Original Message-
From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
Sent: Monday, April 25, 2016 7:19 PM
To: OpenStack Development Mailing List (not for usage questions)

Subject: Re: [openstack-dev] [neutron] Social at the summit

Count me in!
Will be good to meet all you guys!

Darek (dasm) Smigiel


On Apr 25, 2016, at 12:13 PM, Doug Wiegley
 wrote:



On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
wrote:

WAT???

It was never supposed to be core only. Everyone is welcome!


+2

irony intended.

Socials are not controlled by gerrit ACLs.  :-)

doug



Sent from my iPhone


On 25 Apr 2016, at 11:56, Edgar Magana 
wrote:

Would you extend it to ex-cores?

Edgar





On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:

Ihar, Henry and I were talking and we thought Thursday night makes
sense for a Neutron social in Austin. If others agree, reply on this thread
and we'll find a place.

Thanks!
Kyle

___
___ 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 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 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] Social at the summit

[Amitabha Biswas]

+1

AZBiswas

> On Apr 25, 2016, at 1:25 PM, Michael Johnson  wrote:
> 
> +1
> 
> Michael
> 
> On Monday, April 25, 2016, Ananth  > wrote:
> Would be great to connect..
> +1
> 
> Regards
> Ananth
> Cloud & Network Solutions
> Cisco Systems
> 
> On Mon, Apr 25, 2016 at 2:13 PM, Zhipeng Huang  > wrote:
> +1 
> 
> On Mon, Apr 25, 2016 at 1:07 PM, Kyle Mestery  > wrote:
> OK, there is enough interest, I'll find a place on 6th Street for us
> and get a reservation for Thursday around 7 or so.
> 
> Thanks folks!
> 
> On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  > wrote:
> > +1 :)
> >
> > Han Zhou
> > Irc: zhouhan
> >
> >
> > On Monday, April 25, 2016, Korzeniewski, Artur
> >  > > wrote:
> >>
> >> Sign me up :)
> >>
> >> Artur
> >> IRC: korzen
> >>
> >> -Original Message-
> >> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com 
> >> ]
> >> Sent: Monday, April 25, 2016 7:19 PM
> >> To: OpenStack Development Mailing List (not for usage questions)
> >>  >> >
> >> Subject: Re: [openstack-dev] [neutron] Social at the summit
> >>
> >> Count me in!
> >> Will be good to meet all you guys!
> >>
> >> Darek (dasm) Smigiel
> >>
> >> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
> >> >  >> > > wrote:
> >> >
> >> >
> >> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka  >> >> >
> >> >> wrote:
> >> >>
> >> >> WAT???
> >> >>
> >> >> It was never supposed to be core only. Everyone is welcome!
> >> >
> >> > +2
> >> >
> >> > irony intended.
> >> >
> >> > Socials are not controlled by gerrit ACLs.  :-)
> >> >
> >> > doug
> >> >
> >> >>
> >> >> Sent from my iPhone
> >> >>
> >> >>> On 25 Apr 2016, at 11:56, Edgar Magana  >> >>> >
> >> >>> wrote:
> >> >>>
> >> >>> Would you extend it to ex-cores?
> >> >>>
> >> >>> Edgar
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >>  On 4/25/16, 10:55 AM, "Kyle Mestery"  >>  > wrote:
> >> 
> >>  Ihar, Henry and I were talking and we thought Thursday night makes
> >>  sense for a Neutron social in Austin. If others agree, reply on this 
> >>  thread
> >>  and we'll find a place.
> >> 
> >>  Thanks!
> >>  Kyle
> >> 
> >>  ___
> >>  ___ 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 
> >> > 
> >>
> >>
> >> 

Re: [openstack-dev] [neutron] Social at the summit

[M Ranga Swami Reddy]

+1


On Mon, Apr 25, 2016 at 1:07 PM, Kyle Mestery  wrote:
> OK, there is enough interest, I'll find a place on 6th Street for us
> and get a reservation for Thursday around 7 or so.
>
> Thanks folks!
>
> On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
>> +1 :)
>>
>> Han Zhou
>> Irc: zhouhan
>>
>>
>> On Monday, April 25, 2016, Korzeniewski, Artur
>>  wrote:
>>>
>>> Sign me up :)
>>>
>>> Artur
>>> IRC: korzen
>>>
>>> -Original Message-
>>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>>> Sent: Monday, April 25, 2016 7:19 PM
>>> To: OpenStack Development Mailing List (not for usage questions)
>>> 
>>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>>
>>> Count me in!
>>> Will be good to meet all you guys!
>>>
>>> Darek (dasm) Smigiel
>>>
>>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
>>> >  wrote:
>>> >
>>> >
>>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>>> >> wrote:
>>> >>
>>> >> WAT???
>>> >>
>>> >> It was never supposed to be core only. Everyone is welcome!
>>> >
>>> > +2
>>> >
>>> > irony intended.
>>> >
>>> > Socials are not controlled by gerrit ACLs.  :-)
>>> >
>>> > doug
>>> >
>>> >>
>>> >> Sent from my iPhone
>>> >>
>>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>>> >>> wrote:
>>> >>>
>>> >>> Would you extend it to ex-cores?
>>> >>>
>>> >>> Edgar
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>>> 
>>>  Ihar, Henry and I were talking and we thought Thursday night makes
>>>  sense for a Neutron social in Austin. If others agree, reply on this 
>>>  thread
>>>  and we'll find a place.
>>> 
>>>  Thanks!
>>>  Kyle
>>> 
>>>  ___
>>>  ___ 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 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 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] Social at the summit

[Michael Johnson]

+1

Michael

On Monday, April 25, 2016, Ananth  wrote:

> Would be great to connect..
> +1
>
> Regards
> Ananth
> Cloud & Network Solutions
> Cisco Systems
>
> On Mon, Apr 25, 2016 at 2:13 PM, Zhipeng Huang  > wrote:
>
>> +1
>>
>> On Mon, Apr 25, 2016 at 1:07 PM, Kyle Mestery > > wrote:
>>
>>> OK, there is enough interest, I'll find a place on 6th Street for us
>>> and get a reservation for Thursday around 7 or so.
>>>
>>> Thanks folks!
>>>
>>> On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han >> > wrote:
>>> > +1 :)
>>> >
>>> > Han Zhou
>>> > Irc: zhouhan
>>> >
>>> >
>>> > On Monday, April 25, 2016, Korzeniewski, Artur
>>> > >> > wrote:
>>> >>
>>> >> Sign me up :)
>>> >>
>>> >> Artur
>>> >> IRC: korzen
>>> >>
>>> >> -Original Message-
>>> >> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com
>>> ]
>>> >> Sent: Monday, April 25, 2016 7:19 PM
>>> >> To: OpenStack Development Mailing List (not for usage questions)
>>> >> >> >
>>> >> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>> >>
>>> >> Count me in!
>>> >> Will be good to meet all you guys!
>>> >>
>>> >> Darek (dasm) Smigiel
>>> >>
>>> >> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
>>> >> > >> > wrote:
>>> >> >
>>> >> >
>>> >> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka >> >
>>> >> >> wrote:
>>> >> >>
>>> >> >> WAT???
>>> >> >>
>>> >> >> It was never supposed to be core only. Everyone is welcome!
>>> >> >
>>> >> > +2
>>> >> >
>>> >> > irony intended.
>>> >> >
>>> >> > Socials are not controlled by gerrit ACLs.  :-)
>>> >> >
>>> >> > doug
>>> >> >
>>> >> >>
>>> >> >> Sent from my iPhone
>>> >> >>
>>> >> >>> On 25 Apr 2016, at 11:56, Edgar Magana >> >
>>> >> >>> wrote:
>>> >> >>>
>>> >> >>> Would you extend it to ex-cores?
>>> >> >>>
>>> >> >>> Edgar
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >>  On 4/25/16, 10:55 AM, "Kyle Mestery" >> > wrote:
>>> >> 
>>> >>  Ihar, Henry and I were talking and we thought Thursday night
>>> makes
>>> >>  sense for a Neutron social in Austin. If others agree, reply on
>>> this thread
>>> >>  and we'll find a place.
>>> >> 
>>> >>  Thanks!
>>> >>  Kyle
>>> >> 
>>> >> 
>>> ___
>>> >>  ___ 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 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
>>> >> 

Re: [openstack-dev] [neutron] Social at the summit

[Ananth]

Would be great to connect..
+1

Regards
Ananth
Cloud & Network Solutions
Cisco Systems

On Mon, Apr 25, 2016 at 2:13 PM, Zhipeng Huang 
wrote:

> +1
>
> On Mon, Apr 25, 2016 at 1:07 PM, Kyle Mestery  wrote:
>
>> OK, there is enough interest, I'll find a place on 6th Street for us
>> and get a reservation for Thursday around 7 or so.
>>
>> Thanks folks!
>>
>> On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
>> > +1 :)
>> >
>> > Han Zhou
>> > Irc: zhouhan
>> >
>> >
>> > On Monday, April 25, 2016, Korzeniewski, Artur
>> >  wrote:
>> >>
>> >> Sign me up :)
>> >>
>> >> Artur
>> >> IRC: korzen
>> >>
>> >> -Original Message-
>> >> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> >> Sent: Monday, April 25, 2016 7:19 PM
>> >> To: OpenStack Development Mailing List (not for usage questions)
>> >> 
>> >> Subject: Re: [openstack-dev] [neutron] Social at the summit
>> >>
>> >> Count me in!
>> >> Will be good to meet all you guys!
>> >>
>> >> Darek (dasm) Smigiel
>> >>
>> >> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
>> >> >  wrote:
>> >> >
>> >> >
>> >> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> >> wrote:
>> >> >>
>> >> >> WAT???
>> >> >>
>> >> >> It was never supposed to be core only. Everyone is welcome!
>> >> >
>> >> > +2
>> >> >
>> >> > irony intended.
>> >> >
>> >> > Socials are not controlled by gerrit ACLs.  :-)
>> >> >
>> >> > doug
>> >> >
>> >> >>
>> >> >> Sent from my iPhone
>> >> >>
>> >> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >> >>> wrote:
>> >> >>>
>> >> >>> Would you extend it to ex-cores?
>> >> >>>
>> >> >>> Edgar
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> >> 
>> >>  Ihar, Henry and I were talking and we thought Thursday night makes
>> >>  sense for a Neutron social in Austin. If others agree, reply on
>> this thread
>> >>  and we'll find a place.
>> >> 
>> >>  Thanks!
>> >>  Kyle
>> >> 
>> >> 
>> ___
>> >>  ___ 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 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
>>
>
>
>
> --
> Zhipeng (Howard) Huang
>
> Standard Engineer
> IT Standard & Patent/IT Prooduct Line
> Huawei Technologies Co,. Ltd
> Email: huangzhip...@huawei.com
> Office: Huawei Industrial Base, Longgang, Shenzhen
>
> 

Re: [openstack-dev] [neutron] Social at the summit

[Robert Kukura]

+1

On 4/25/16 1:07 PM, Kyle Mestery wrote:

OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:

+1 :)

Han Zhou
Irc: zhouhan


On Monday, April 25, 2016, Korzeniewski, Artur
 wrote:

Sign me up :)

Artur
IRC: korzen

-Original Message-
From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
Sent: Monday, April 25, 2016 7:19 PM
To: OpenStack Development Mailing List (not for usage questions)

Subject: Re: [openstack-dev] [neutron] Social at the summit

Count me in!
Will be good to meet all you guys!

Darek (dasm) Smigiel


On Apr 25, 2016, at 12:13 PM, Doug Wiegley
 wrote:



On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
wrote:

WAT???

It was never supposed to be core only. Everyone is welcome!

+2

irony intended.

Socials are not controlled by gerrit ACLs.  :-)

doug


Sent from my iPhone


On 25 Apr 2016, at 11:56, Edgar Magana 
wrote:

Would you extend it to ex-cores?

Edgar





On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:

Ihar, Henry and I were talking and we thought Thursday night makes
sense for a Neutron social in Austin. If others agree, reply on this thread
and we'll find a place.

Thanks!
Kyle

___
___ 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 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 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] [Fuel] Newton Design Summit sessions planning

[Vladimir Kozhukalov]

​Done.

Wed 11:00-11:40 Finalizing of HA reference architecture with event-based
control and fencing
Thu 11:00-11:40 Fuel UI Modularization approaches discussion

Vladimir Kozhukalov

On Mon, Apr 25, 2016 at 10:14 PM, Vladimir Kuklin 
wrote:

> Fuelers
>
> I am OK with the proposed change
> 21 апр. 2016 г. 12:34 пользователь "Vitaly Kramskikh" <
> vkramsk...@mirantis.com> написал:
>
> Folks,
>>
>> I'd like to request workroom sessions swap.
>>
>> I planned to lead a discussion of Fuel UI modularization on Wed
>> 11.00-11.40, but at the same time there will be discussion of handling JS
>> dependencies of Horizon which I'd really like to attend.
>>
>> So I request to swap my discussion with discussion of finalizing of HA
>> reference architecture with event-based control and fencing led by V.
>> Kuklin on Thu 11.00-11.40.
>>
>> Do you have any objections?
>>
>> 2016-04-14 17:55 GMT+03:00 Alexey Shtokolov :
>>
>>> Hi, +1 from my side.
>>>
>>> ---
>>> WBR, Alexey Shtokolov
>>>
>>> 2016-04-14 16:47 GMT+03:00 Evgeniy L :
>>>
 Hi, no problem from my side.

 On Thu, Apr 14, 2016 at 10:53 AM, Vladimir Kozhukalov <
 vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> I'd like to request workrooms sessions swap.
>
> We have a session about Fuel/Ironic integration and I'd like
> this session not to overlap with Ironic sessions, so Ironic
> team could attend Fuel sessions. At the same time, we have
> a session about orchestration engine and it would be great to
> invite there people from Mistral and Heat.
>
> My suggestion is as follows:
>
> Wed:
> 9:50 Astute -> Mistral/Heat/???
> Thu:
> 9.00 Fuel/Ironic/Ironic-inspector
>
> If there are any objections, please let me know asap.
>
>
>
> Vladimir Kozhukalov
>
> On Fri, Apr 1, 2016 at 9:47 PM, Vladimir Kozhukalov <
> vkozhuka...@mirantis.com> wrote:
>
>> Dear colleagues,
>>
>> Looks like we have final version sessions layout [1]
>> for Austin design summit. We have 3 fishbows,
>> 11 workrooms, full day meetup.
>>
>> Here you can find some useful information about design
>> summit [2]. All session leads must read this page,
>> be prepared for their sessions (agenda, slides if needed,
>> etherpads for collaborative work, etc.) and follow
>> the recommendations given in "At the Design Summit" section.
>>
>> Here is Fuel session planning etherpad [3]. Almost all suggested
>> topics have been put there. Please put links to slide decks
>> and etherpads next to respective sessions. Here is the
>> page [4] where other teams publish their planning pads.
>>
>> If session leads want for some reason to swap their slots it must
>> be requested in this ML thread. If for some reason session lead
>> can not lead his/her session, it must be announced in this ML thread.
>>
>> Fuel sessions are:
>> ===
>> Fishbowls:
>> ===
>> Wed:
>> 15:30-16:10
>> 16:30:17:10
>> 17:20-18:00
>>
>> ===
>> Workrooms:
>> ===
>> Wed:
>> 9:00-9:40
>> 9:50-10:30
>> 11:00-11:40
>> 11:50-12:30
>> 13:50-14:30
>> 14:40-15:20
>> Thu:
>> 9:00-9:40
>> 9:50-10:30
>> 11:00-11:40
>> 11:50-12:30
>> 13:30-14:10
>>
>> ===
>> Meetup:
>> ===
>> Fri:
>> 9:00-12:30
>> 14:00-17:30
>>
>> [1]
>> http://lists.openstack.org/pipermail/openstack-dev/attachments/20160331/d59d38b7/attachment.pdf
>> [2] https://wiki.openstack.org/wiki/Design_Summit
>> [3] https://etherpad.openstack.org/p/fuel-newton-summit-planning
>> [4] https://wiki.openstack.org/wiki/Design_Summit/Planning
>>
>> Thanks.
>>
>> Vladimir Kozhukalov
>>
>
>
>
> __
> 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
>>>
>>>
>>
>>
>> --
>> Vitaly Kramskikh,
>> Fuel UI Tech Lead,
>> Mirantis, Inc.
>>
>

[openstack-dev] [HA] Watcher Meethings

[Sam P]

Hi all,

 In Austin summit, Susanne Balle (with Watcher team)  invite HA people
to come to Watcher sessions and discuss the use case.

 FYI, here are the watcher sessions and mail they sent to watcher team.

On Fri, Apr 22, 2016 at 12:37 PM, Antoine Cabot
 wrote:
> Hi Watcher team,
>
> We will have a couple of meetings next week to discuss Watcher
> achievements during the Mitaka cycle and define priorities for Newton.
>
> Meetings will be held in the developer lounge in Austin
> https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Watcher
>
> A proposed open agenda is available
> https://etherpad.openstack.org/p/watcher-newton-design-session
>
> If you want to meet with Watcher team and discuss your use cases,
> feel free to join us and add your discussion topic to the agenda.
>
> Thanks,
>
> Antoine (acabot)


--- Regards,
 SamP

__
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] Social at the summit

[Zhipeng Huang]

+1

On Mon, Apr 25, 2016 at 1:07 PM, Kyle Mestery  wrote:

> OK, there is enough interest, I'll find a place on 6th Street for us
> and get a reservation for Thursday around 7 or so.
>
> Thanks folks!
>
> On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> > +1 :)
> >
> > Han Zhou
> > Irc: zhouhan
> >
> >
> > On Monday, April 25, 2016, Korzeniewski, Artur
> >  wrote:
> >>
> >> Sign me up :)
> >>
> >> Artur
> >> IRC: korzen
> >>
> >> -Original Message-
> >> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
> >> Sent: Monday, April 25, 2016 7:19 PM
> >> To: OpenStack Development Mailing List (not for usage questions)
> >> 
> >> Subject: Re: [openstack-dev] [neutron] Social at the summit
> >>
> >> Count me in!
> >> Will be good to meet all you guys!
> >>
> >> Darek (dasm) Smigiel
> >>
> >> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
> >> >  wrote:
> >> >
> >> >
> >> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
> >> >> wrote:
> >> >>
> >> >> WAT???
> >> >>
> >> >> It was never supposed to be core only. Everyone is welcome!
> >> >
> >> > +2
> >> >
> >> > irony intended.
> >> >
> >> > Socials are not controlled by gerrit ACLs.  :-)
> >> >
> >> > doug
> >> >
> >> >>
> >> >> Sent from my iPhone
> >> >>
> >> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
> >> >>> wrote:
> >> >>>
> >> >>> Would you extend it to ex-cores?
> >> >>>
> >> >>> Edgar
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
> >> 
> >>  Ihar, Henry and I were talking and we thought Thursday night makes
> >>  sense for a Neutron social in Austin. If others agree, reply on
> this thread
> >>  and we'll find a place.
> >> 
> >>  Thanks!
> >>  Kyle
> >> 
> >>  ___
> >>  ___ 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 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
>



-- 
Zhipeng (Howard) Huang

Standard Engineer
IT Standard & Patent/IT Prooduct Line
Huawei Technologies Co,. Ltd
Email: huangzhip...@huawei.com
Office: Huawei Industrial Base, Longgang, Shenzhen

(Previous)
Research Assistant
Mobile Ad-Hoc Network Lab, Calit2
University of California, Irvine
Email: zhipe...@uci.edu
Office: Calit2 Building Room 2402

OpenStack, OPNFV, OpenDaylight, OpenCompute Aficionado
__
OpenStack Development Mailing List (not for usage 

Re: [openstack-dev] [Fuel] Newton Design Summit sessions planning

[Vladimir Kuklin]

Fuelers

I am OK with the proposed change
21 апр. 2016 г. 12:34 пользователь "Vitaly Kramskikh" <
vkramsk...@mirantis.com> написал:

> Folks,
>
> I'd like to request workroom sessions swap.
>
> I planned to lead a discussion of Fuel UI modularization on Wed
> 11.00-11.40, but at the same time there will be discussion of handling JS
> dependencies of Horizon which I'd really like to attend.
>
> So I request to swap my discussion with discussion of finalizing of HA
> reference architecture with event-based control and fencing led by V.
> Kuklin on Thu 11.00-11.40.
>
> Do you have any objections?
>
> 2016-04-14 17:55 GMT+03:00 Alexey Shtokolov :
>
>> Hi, +1 from my side.
>>
>> ---
>> WBR, Alexey Shtokolov
>>
>> 2016-04-14 16:47 GMT+03:00 Evgeniy L :
>>
>>> Hi, no problem from my side.
>>>
>>> On Thu, Apr 14, 2016 at 10:53 AM, Vladimir Kozhukalov <
>>> vkozhuka...@mirantis.com> wrote:
>>>
 Dear colleagues,

 I'd like to request workrooms sessions swap.

 We have a session about Fuel/Ironic integration and I'd like
 this session not to overlap with Ironic sessions, so Ironic
 team could attend Fuel sessions. At the same time, we have
 a session about orchestration engine and it would be great to
 invite there people from Mistral and Heat.

 My suggestion is as follows:

 Wed:
 9:50 Astute -> Mistral/Heat/???
 Thu:
 9.00 Fuel/Ironic/Ironic-inspector

 If there are any objections, please let me know asap.



 Vladimir Kozhukalov

 On Fri, Apr 1, 2016 at 9:47 PM, Vladimir Kozhukalov <
 vkozhuka...@mirantis.com> wrote:

> Dear colleagues,
>
> Looks like we have final version sessions layout [1]
> for Austin design summit. We have 3 fishbows,
> 11 workrooms, full day meetup.
>
> Here you can find some useful information about design
> summit [2]. All session leads must read this page,
> be prepared for their sessions (agenda, slides if needed,
> etherpads for collaborative work, etc.) and follow
> the recommendations given in "At the Design Summit" section.
>
> Here is Fuel session planning etherpad [3]. Almost all suggested
> topics have been put there. Please put links to slide decks
> and etherpads next to respective sessions. Here is the
> page [4] where other teams publish their planning pads.
>
> If session leads want for some reason to swap their slots it must
> be requested in this ML thread. If for some reason session lead
> can not lead his/her session, it must be announced in this ML thread.
>
> Fuel sessions are:
> ===
> Fishbowls:
> ===
> Wed:
> 15:30-16:10
> 16:30:17:10
> 17:20-18:00
>
> ===
> Workrooms:
> ===
> Wed:
> 9:00-9:40
> 9:50-10:30
> 11:00-11:40
> 11:50-12:30
> 13:50-14:30
> 14:40-15:20
> Thu:
> 9:00-9:40
> 9:50-10:30
> 11:00-11:40
> 11:50-12:30
> 13:30-14:10
>
> ===
> Meetup:
> ===
> Fri:
> 9:00-12:30
> 14:00-17:30
>
> [1]
> http://lists.openstack.org/pipermail/openstack-dev/attachments/20160331/d59d38b7/attachment.pdf
> [2] https://wiki.openstack.org/wiki/Design_Summit
> [3] https://etherpad.openstack.org/p/fuel-newton-summit-planning
> [4] https://wiki.openstack.org/wiki/Design_Summit/Planning
>
> Thanks.
>
> Vladimir Kozhukalov
>



 __
 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
>>
>>
>
>
> --
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>
__
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] [watcher] Watcher meetings in Austin

[Joe Cropper]

Hi Watcher team,

Resending this in case folks missed it.

Thanks,

Joe (jwcroppe)


> On Apr 22, 2016, at 4:37 AM, Antoine Cabot  wrote:
> 
> Hi Watcher team,
> 
> We will have a couple of meetings next week to discuss Watcher
> achievements during the Mitaka cycle and define priorities for Newton.
> 
> Meetings will be held in the developer lounge in Austin
> https://wiki.openstack.org/wiki/Design_Summit/Newton/Etherpads#Watcher
> 
> A proposed open agenda is available
> https://etherpad.openstack.org/p/watcher-newton-design-session
> 
> If you want to meet with Watcher team and discuss your use cases,
> feel free to join us and add your discussion topic to the agenda.
> 
> Thanks,
> 
> Antoine (acabot)
> 
> __
> 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] [searchlight] [ceilometer] [fuel] [freezer] [monasca] Elasticsearch 2.x gate support

[gordon chung]

On 24/04/2016 6:53 PM, Julien Danjou wrote:
> On Mon, Apr 18 2016, McLellan, Steven wrote:
>
> Hi Steven,
>
> […]
>
>> * Have you tested with ES 2.x at all?
>> * Do you have plans to move to ES 2.x?
>
> I don't think we have tested that nor anyone working actively on ES.
> Gordon Chung is probably the more knowledgeable on that piece.
>
> Though I would not want Ceilometer to block any other project going to
> be heavily relying on ES. So if nobody steps up to update Ceilometer for
> ES 2, we can also look into deprecating the driver.
>
> I'll let Gordon weight in.
>

i haven't tried 2.x personally. we use pretty standard functionality for 
ElasticSearch driver and at quick glance, it seems like all the apis 
still exist.

i agree with jd, feel free to bump and we'll deal with the effects.

i guess the only question i have is whether ES 2.x is even an option? is 
it packaged by distro or are they still using 1.x?

cheers,

-- 
gord

__
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] [heat]informal meetup during summit

[Zane Bitter]

Thanks for organising Rico! See you when you get there.

- ZB


On 22/04/16 20:01, Rico Lin wrote:

Let's settle down on with

A meet up on Monday night 7:00pm
At continentalclub

address : 1315 S Congress Ave
Austin, TX 78704 http://continentalclub.com

And
Friday morning 10:00 venue:TBD

Is the time and venue find with everyone?

Everyone are welcome :)
Feel free to let me know if you're coming, just for easy pre-booking
purpose:)

On Apr 22, 2016 12:13 AM, "Zane Bitter" > wrote:

On 20/04/16 13:00, Rico Lin wrote:

Hi team
Let plan for more informal meetup(relax) time! Let all heaters
and any
other projects can have fun and chance for technical discussions
together.

After discuss in meeting, we will have a pre-meetup-meetup on Friday
morning to have a cup of cafe or some food. Would like to ask if
anyone
knows any nice place for this meetup?:)


According to
https://www.openstack.org/summit/austin-2016/guide-to-austin/ if we
line up at Franklin's at 7am then we can be eating barbeque by 11
and still make it back in time for the afternoon meetup :))

Also open for other chance for all can go out for a nice dinner and
beer. Right now seems maybe Monday or Friday night could be the best
candidate for this wonderful task, what all think about this? :)


+1. I'll be around on Friday, but I imagine a few people will be
leaving so Monday is probably better.

cheers,
Zane.

__
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] [OpenStack][Neutron][Monasca] Traffic counters at Layer 3

[Rubab Syed]

Hi folks,

I'm writing a plugin for Monasca to monitor traffic at layer 3. My Neutron
backend is OVS and I'm using iptables of network namespaces for getting
traffic counters. Would the following rules in router namespace cover all
the traffic at layer 3 per router per tenant?

- Chain MONASCA-INPUT in filter table
   - src: anywhere dest: gateway port IP   // north-south traffic for
SNATed and FIPs

- Chain MONASCA-FORWARD in filter table
  - src: anywhere   dest: anywhere  // east-west traffic
inter-network and intra-network

- Chain MONASCA-OUTPUT in filter table
  - src: gateway port dest: anywhere  // north-south traffic from
VMs to public network


Would these be sufficient or am I missing something?

Thanks!

Rubab
__
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][vpnaas] VPNaaS tox api failure

[Bharath Kumar Gubbala]

Hi Henry,


Do you have any info on below query in the thread.(is 'tox -e api' working in 
neutron-vpnaas ?)



Thanks,

bharath



From: bharath 
Sent: 08 April 2016 01:53
To: OpenStack Development Mailing List (not for usage questions); Alex 
Geevarghese; madhusudhan.openst...@gmail.com; p...@michali.net
Subject: Re: [openstack-dev] [neutron][vpnaas] VPNaaS tox api failure

Thanks Paul for info.

Yes i had run the tests locally under VPN-repo.

My analysis:

  *   VPN test cases were using the neutron client for VPN services 
(which no longer supported by neutron).

 Thats why its throwing "tempest.lib.exceptions.NotFound: 
Object not found"

  *   In the case of FW , there were using router client directly 
instead of neutron client.


I will check with madhusudhan for additional info.



Madhu,
Let me know if you have info on "tox api" support.
If it is an known issue, i can take it up and complete fix

Thanks,
bharath




On Friday 08 April 2016 01:00 AM, Paul Michali wrote:
Are you running the test locally?

IIRC, the tempest based API tests for VPN have been (are being) moved to the 
VPN repo, but I don't know if a job was ever created for this so that the tests 
actually run. You may want to check with the author who moved the tests 
(madhusudan-kandadai) under commit 3cae934a, to see if the CI job was ever 
created. It is possible that it was never completed.

Likewise, I don't know if support was added to tox.ini for the api test. I've 
never run the test, granted I've been away from VPN for a while and only 
involved intermittently since Liberty, so I may be a bit out of touch.

Regards,

PCM


On Thu, Apr 7, 2016 at 2:23 PM bharath 
> wrote:

Hi,

While running "tox -e api" i hitting " tempest.lib.NotFound" Error.

Is it a known issue ? failures expected?

https://review.openstack.org/#/c/291949/1
  ==> In this commit messages it says it kindof expected failure.

Can someone provide some clarification on this

Thanks,
bharath
__
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
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev=CwICAg=IL_XqQWOjubgfqINi2jTzg=87NL1fmn9sX2yN6wRmckSjVQpenT6rqPI7fvK0O5yfk=9pS9SGHSr62ETR_Qt_kSEpw9f-DjUThD6EYZ90W4cyU=ajURyED5NOlDi3x19ZS_layCPNAtjp7vjElGBLVMOtQ=


__
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] Social at the summit

[Kyle Mestery]

OK, there is enough interest, I'll find a place on 6th Street for us
and get a reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> +1 :)
>
> Han Zhou
> Irc: zhouhan
>
>
> On Monday, April 25, 2016, Korzeniewski, Artur
>  wrote:
>>
>> Sign me up :)
>>
>> Artur
>> IRC: korzen
>>
>> -Original Message-
>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> Sent: Monday, April 25, 2016 7:19 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> 
>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>
>> Count me in!
>> Will be good to meet all you guys!
>>
>> Darek (dasm) Smigiel
>>
>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley
>> >  wrote:
>> >
>> >
>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> wrote:
>> >>
>> >> WAT???
>> >>
>> >> It was never supposed to be core only. Everyone is welcome!
>> >
>> > +2
>> >
>> > irony intended.
>> >
>> > Socials are not controlled by gerrit ACLs.  :-)
>> >
>> > doug
>> >
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >>> wrote:
>> >>>
>> >>> Would you extend it to ex-cores?
>> >>>
>> >>> Edgar
>> >>>
>> >>>
>> >>>
>> >>>
>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>>  Ihar, Henry and I were talking and we thought Thursday night makes
>>  sense for a Neutron social in Austin. If others agree, reply on this 
>>  thread
>>  and we'll find a place.
>> 
>>  Thanks!
>>  Kyle
>> 
>>  ___
>>  ___ 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 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

Re: [openstack-dev] [neutron] Social at the summit

[Zhou, Han]

+1 :)

Han Zhou
Irc: zhouhan

On Monday, April 25, 2016, Korzeniewski, Artur 
wrote:

> Sign me up :)
>
> Artur
> IRC: korzen
>
> -Original Message-
> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com ]
> Sent: Monday, April 25, 2016 7:19 PM
> To: OpenStack Development Mailing List (not for usage questions) <
> openstack-dev@lists.openstack.org >
> Subject: Re: [openstack-dev] [neutron] Social at the summit
>
> Count me in!
> Will be good to meet all you guys!
>
> Darek (dasm) Smigiel
>
> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley  > wrote:
> >
> >
> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka  > wrote:
> >>
> >> WAT???
> >>
> >> It was never supposed to be core only. Everyone is welcome!
> >
> > +2
> >
> > irony intended.
> >
> > Socials are not controlled by gerrit ACLs.  :-)
> >
> > doug
> >
> >>
> >> Sent from my iPhone
> >>
> >>> On 25 Apr 2016, at 11:56, Edgar Magana  > wrote:
> >>>
> >>> Would you extend it to ex-cores?
> >>>
> >>> Edgar
> >>>
> >>>
> >>>
> >>>
>  On 4/25/16, 10:55 AM, "Kyle Mestery"  > wrote:
> 
>  Ihar, Henry and I were talking and we thought Thursday night makes
> sense for a Neutron social in Austin. If others agree, reply on this thread
> and we'll find a place.
> 
>  Thanks!
>  Kyle
> 
>  ___
>  ___ 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 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] Social at the summit

[Korzeniewski, Artur]

Sign me up :)

Artur
IRC: korzen

-Original Message-
From: Darek Smigiel [mailto:smigiel.dari...@gmail.com] 
Sent: Monday, April 25, 2016 7:19 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] Social at the summit

Count me in!
Will be good to meet all you guys!

Darek (dasm) Smigiel

> On Apr 25, 2016, at 12:13 PM, Doug Wiegley  
> wrote:
> 
> 
>> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka  wrote:
>> 
>> WAT???
>> 
>> It was never supposed to be core only. Everyone is welcome!
> 
> +2
> 
> irony intended.
> 
> Socials are not controlled by gerrit ACLs.  :-)
> 
> doug
> 
>> 
>> Sent from my iPhone
>> 
>>> On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
>>> 
>>> Would you extend it to ex-cores?
>>> 
>>> Edgar
>>> 
>>> 
>>> 
>>> 
 On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
 
 Ihar, Henry and I were talking and we thought Thursday night makes sense 
 for a Neutron social in Austin. If others agree, reply on this thread and 
 we'll find a place.
 
 Thanks!
 Kyle
 
 ___
 ___ 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 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] Social at the summit

[Darek Smigiel]

Count me in!
Will be good to meet all you guys!

Darek (dasm) Smigiel

> On Apr 25, 2016, at 12:13 PM, Doug Wiegley  
> wrote:
> 
> 
>> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka  wrote:
>> 
>> WAT???
>> 
>> It was never supposed to be core only. Everyone is welcome!
> 
> +2
> 
> irony intended.
> 
> Socials are not controlled by gerrit ACLs.  :-)
> 
> doug
> 
>> 
>> Sent from my iPhone
>> 
>>> On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
>>> 
>>> Would you extend it to ex-cores?
>>> 
>>> Edgar
>>> 
>>> 
>>> 
>>> 
 On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
 
 Ihar, Henry and I were talking and we thought Thursday night makes sense 
 for a Neutron social in Austin. If others agree, reply on this thread and 
 we'll find a place.
 
 Thanks!
 Kyle
 
 __
 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 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] Social at the summit

[Oleg Bondarev]

Count me in!

On Mon, Apr 25, 2016 at 10:01 AM, Ihar Hrachyshka 
wrote:

> WAT???
>
> It was never supposed to be core only. Everyone is welcome!
>

++


> Sent from my iPhone
>
> > On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
> >
> > Would you extend it to ex-cores?
> >
> > Edgar
> >
> >
> >
> >
> >> On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
> >>
> >> Ihar, Henry and I were talking and we thought Thursday night makes
> sense for a Neutron social in Austin. If others agree, reply on this thread
> and we'll find a place.
> >>
> >> Thanks!
> >> Kyle
> >>
> >>
> __
> >> 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

Re: [openstack-dev] [neutron] Social at the summit

[Doug Wiegley]

> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka  wrote:
> 
> WAT???
> 
> It was never supposed to be core only. Everyone is welcome!

+2

irony intended.

Socials are not controlled by gerrit ACLs.  :-)

doug

> 
> Sent from my iPhone
> 
>> On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
>> 
>> Would you extend it to ex-cores?
>> 
>> Edgar
>> 
>> 
>> 
>> 
>>> On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>>> 
>>> Ihar, Henry and I were talking and we thought Thursday night makes sense 
>>> for a Neutron social in Austin. If others agree, reply on this thread and 
>>> we'll find a place.
>>> 
>>> Thanks!
>>> Kyle
>>> 
>>> __
>>> 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

Re: [openstack-dev] [neutron] Social at the summit

[Edgar Magana]

I know! Just having fun and teasing Kyle. ;-)

Sent from my iPhone

> On Apr 25, 2016, at 12:08 PM, Ihar Hrachyshka  wrote:
> 
> WAT???
> 
> It was never supposed to be core only. Everyone is welcome!
> 
> Sent from my iPhone
> 
>> On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
>> 
>> Would you extend it to ex-cores?
>> 
>> Edgar
>> 
>> 
>> 
>> 
>>> On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>>> 
>>> Ihar, Henry and I were talking and we thought Thursday night makes sense 
>>> for a Neutron social in Austin. If others agree, reply on this thread and 
>>> we'll find a place.
>>> 
>>> Thanks!
>>> Kyle
>>> 
>>> __
>>> 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

Re: [openstack-dev] [neutron] Social at the summit

[Ihar Hrachyshka]

WAT???

It was never supposed to be core only. Everyone is welcome!

Sent from my iPhone

> On 25 Apr 2016, at 11:56, Edgar Magana  wrote:
> 
> Would you extend it to ex-cores?
> 
> Edgar
> 
> 
> 
> 
>> On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>> Ihar, Henry and I were talking and we thought Thursday night makes sense for 
>> a Neutron social in Austin. If others agree, reply on this thread and we'll 
>> find a place.
>> 
>> Thanks!
>> Kyle
>> 
>> __
>> 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] Social at the summit

[Edgar Magana]

Would you extend it to ex-cores?

Edgar




On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:

>Ihar, Henry and I were talking and we thought Thursday night makes sense for a 
>Neutron social in Austin. If others agree, reply on this thread and we'll find 
>a place.
>
>Thanks!
>Kyle
>
>__
>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] Encrypted Ephemeral Storage

[Daniel P. Berrange]

On Mon, Apr 25, 2016 at 04:28:17PM +, Coffman, Joel M. wrote:
> Based on the comments to the RBD encryption change [1], it looks
> like there will be a new direction for ephemeral disk encryption
> (embedding it in QEMU directly). I assume LVM will work the same
> way when the time comes. Will there be a migration path for the
> existing ephemeral disk encryption support for LVM to the new
> model?
> 
> [1] https://review.openstack.org/#/c/239798/
> 
> Yes, as I understand it, the long-term goal is to provide encryption
> support directly in QEMU and have a unified interface for LVM, RBD,
> and file-based backends. I do not yet know what the potential
> migration path will look like.

The forthcoming QEMU 2.6 release will include native support for the
LUKS data format. There is a test suite with QEMU to prove that this
is interoperable with the kernel dm-crypt/cryptsetup tools. So there
will be no data migration required. Nova will merely need to change
the way it configures to point QEMU directly to the encrypted LVM
volume, instead of creating a dm-crypt volume wrapper. QEMU will
then directly decrypt the LVM volume.

Regards,
Daniel
-- 
|: http://berrange.com  -o-http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org  -o- http://virt-manager.org :|
|: http://autobuild.org   -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org   -o-   http://live.gnome.org/gtk-vnc :|

__
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] Social at the summit

[Doug Wiegley]

I’m in.

> On Apr 25, 2016, at 11:24 AM, Martin Hickey  wrote:
> 
> +1
> 
> Regards,
> Martin
> -
> Martin Hickey | Software Development | OpenStack | Tel: + 353 21 7306040 
> 
> Nate Johnston ---25/04/2016 10:58:21---Count me in. --N.
> 
> From: Nate Johnston 
> To: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Date: 25/04/2016 10:58
> Subject: Re: [openstack-dev] [neutron] Social at the summit
> 
> 
> 
> 
> Count me in. 
> 
> --N.
> 
> On Monday, April 25, 2016, Kyle Mestery  > wrote:
> Ihar, Henry and I were talking and we thought Thursday night makes sense for 
> a Neutron social in Austin. If others agree, reply on this thread and we'll 
> find a place.
> 
> Thanks!
> Kyle
> 
> __
> 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

Re: [openstack-dev] [Fuel] Fuel 9.0 is released

[Daniele Pizzolli]

On Mon, Apr 25 2016, you wrote:

> Can we support alternative way to download ISO since p2p may be prevented in 
> some company IT?

Hello,

It is supported... but not advertised. I am not sure if this is by
purpose (maybe because in http there is no additional checksum, see
later for offline verification). For example to download:

fuel-community-9.0.iso.torrent 

you can use http:

http://seed-cz1.fuel-infra.org/fuelweb-community-release/fuel-community-9.0.iso
http://seed-us1.fuel-infra.org/fuelweb-community-release/fuel-community-9.0.iso

You can get the links by yourself, by getting the torrent and for
example using:

set -- fuel-community-9.0.iso.torrent
aria2c --show-files -- "$1" \
| awk '/^[a-zA-Z]/{p=0};/^URL List:/{q=1};/^ http/{p=1};p&{print $1}'

Sorry for the heavy awk usage... I do not know a simple way to print
them!  Maybe some bittorrent client has an option for that.

If you are able to get the torrent file, you can also verify the
checksum off line, for example by using btcheck.

>
> Thanks,

Best,
Daniele

__
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] Social at the summit

[Martin Hickey]

+1

Regards,
Martin
-
Martin Hickey | Software Development | OpenStack | Tel: + 353 21 7306040



From:   Nate Johnston 
To: "OpenStack Development Mailing List (not for usage questions)"

Date:   25/04/2016 10:58
Subject:Re: [openstack-dev] [neutron] Social at the summit



Count me in.

--N.

On Monday, April 25, 2016, Kyle Mestery  wrote:
  Ihar, Henry and I were talking and we thought Thursday night makes sense
  for a Neutron social in Austin. If others agree, reply on this thread and
  we'll find a place.

  Thanks!
  Kyle

  __

  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] Encrypted Ephemeral Storage

[Coffman, Joel M.]

Based on the comments to the RBD encryption change [1], it looks like there 
will be a new direction for ephemeral disk encryption (embedding it in QEMU 
directly). I assume LVM will work the same way when the time comes. Will there 
be a migration path for the existing ephemeral disk encryption support for LVM 
to the new model?

[1] https://review.openstack.org/#/c/239798/

Yes, as I understand it, the long-term goal is to provide encryption support 
directly in QEMU and have a unified interface for LVM, RBD, and file-based 
backends. I do not yet know what the potential migration path will look like.

__
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] Social at the summit

[Neil Jerram]

On 25/04/16 10:58, Kyle Mestery wrote:
> Ihar, Henry and I were talking and we thought Thursday night makes sense for 
> a Neutron social in Austin. If others agree, reply on this thread and we'll 
> find a place.

That sounds good to me - thanks for thinking of it!

Neil



__
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] Social at the summit

[Nate Johnston]

Count me in.

--N.

On Monday, April 25, 2016, Kyle Mestery  wrote:

> Ihar, Henry and I were talking and we thought Thursday night makes sense
> for a Neutron social in Austin. If others agree, reply on this thread and
> we'll find a place.
>
> Thanks!
> Kyle
>
> __
> 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] Social at the summit

[Kyle Mestery]

Ihar, Henry and I were talking and we thought Thursday night makes sense for a 
Neutron social in Austin. If others agree, reply on this thread and we'll find 
a place.

Thanks!
Kyle

__
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] Encrypted Ephemeral Storage

[Chris Buccella]

Thanks Joel. I was able to try this again and can confirm it works as you
describe. Cool.

Based on the comments to the RBD encryption change [1], it looks like there
will be a new direction for ephemeral disk encryption (embedding it in QEMU
directly). I assume LVM will work the same way when the time comes. Will
there be a migration path for the existing ephemeral disk encryption
support for LVM to the new model?


-Chris

[1] https://review.openstack.org/#/c/239798/



On Thu, Apr 14, 2016 at 12:56 PM, Coffman, Joel M. 
wrote:

> > Upon reading the source, I don't see "cryptsetup luksFormat" being
> called anywhere (nova/libvirt/storage/*).
> Check out imagebackend.py:Lvm.create_image
> 
>  and dmcrypt.py:create_volume
> 
> .
>
> > How is this feature envisioned to work?
> The LVM volume with the '-dmcrypt' suffix is the *unencrypted* device
> that is passed to the VM. From a DevStack machine with an encrypted
> instance:
>
> *$* sudo cryptsetup status
> /dev/mapper/065859b2-50d6-46d6-927a-2dfd07db3306_disk-dmcrypt
>
> /dev/mapper/065859b2-50d6-46d6-927a-2dfd07db3306_disk-dmcrypt is active
> and is in use.
>
>   type:PLAIN
>
>   cipher:  aes-xts-plain64
>
>   keysize: 256 bits
>
>   device:
> /dev/mapper/stack--volumes--default-065859b2--50d6--46d6--927a--2dfd07db3306_disk
>
>   offset:  0 sectors
>
>   size:2097152 sectors
>
>   mode:read/write
>
> *$* sudo fuser -vam
> /dev/mapper/065859b2-50d6-46d6-927a-2dfd07db3306_disk-dmcrypt
>
>  USERPID ACCESS COMMAND
>
> /dev/dm-1:   libvirt-qemu   8429 F qemu-system-x86
> While information in the '*-dmcrypt' device is visible to a root user on
> the compute host, the underlying device (stack--volumes--default-* in the
> example above) is encrypted, and everything written to the underlying disk
> is also encrypted. Try searching for the text in the underlying device –
> you shouldn't be able to find it.
>
> Joel
>
>
> From: Chris Buccella 
> Reply-To: "openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> Date: Monday, April 11, 2016 at 1:06 PM
> To: "openstack-dev@lists.openstack.org"  >
> Subject: [openstack-dev] [nova] Encrypted Ephemeral Storage
>
> I've been looking into using encrypted ephemeral storage with LVM. With
> the [ephemeral_storage_encryption] and [keymgr] sections to nova.conf, I
> get an LVM volume with "-dmcrypt" is appended to the volume name, but
> otherwise see no difference; I can still grep for text inside the volume.
>
> Upon reading the source, I don't see "cryptsetup luksFormat" being called
> anywhere (nova/libvirt/storage/*).
>
> I was expecting a new encrypted LVM volume when a new instance was
> created. Are my expectations misplaced? How is this feature envisioned to
> work?
>
>
> Thanks,
>
> -Chris
>
> __
> 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] [heat]informal meetup during summit

[Ethan Lynn]

Have a company social tonight, will join you at Friday :)


Best Regards,
Ethan Lynn
xuanlangj...@gmail.com




> On Apr 24, 2016, at 10:28, Rico Lin  wrote:
> 
> Hi all
> Let's settle with fallowing schedule:)
> 
> Monday 7:00 pm at 
>  continentalclub 
> 
>  : The most recommanded place for live music bar in Austin!
> address : 1315 S Congress Ave
> Austin, TX 78704 http://continentalclub.com 
> 
> (Feel free to get there early, will be there around 7)
> 
> 
> Friday 10:00 am at alta's cafe
> http://altascafe.com/ 
> map 
> 
> 
> See you all there:)
> 
> 2016-04-23 9:01 GMT+08:00 Rico Lin  >:
> Let's settle down on with
> 
> A meet up on Monday night 7:00pm
> At  continentalclub 
> 
>  address : 1315 S Congress Ave
> Austin, TX 78704 http://continentalclub.com 
> 
> And 
> Friday morning 10:00 venue:TBD
> 
> Is the time and venue find with everyone?
> 
> Everyone are welcome :)
> Feel free to let me know if you're coming, just for easy pre-booking purpose:)
> 
> On Apr 22, 2016 12:13 AM, "Zane Bitter"  > wrote:
> On 20/04/16 13:00, Rico Lin wrote:
> Hi team
> Let plan for more informal meetup(relax) time! Let all heaters and any
> other projects can have fun and chance for technical discussions together.
> 
> After discuss in meeting, we will have a pre-meetup-meetup on Friday
> morning to have a cup of cafe or some food. Would like to ask if anyone
> knows any nice place for this meetup?:)
> 
> According to https://www.openstack.org/summit/austin-2016/guide-to-austin/ 
>  if we line up 
> at Franklin's at 7am then we can be eating barbeque by 11 and still make it 
> back in time for the afternoon meetup :))
> 
> Also open for other chance for all can go out for a nice dinner and
> beer. Right now seems maybe Monday or Friday night could be the best
> candidate for this wonderful task, what all think about this? :)
> 
> +1. I'll be around on Friday, but I imagine a few people will be leaving so 
> Monday is probably better.
> 
> cheers,
> Zane.
> 
> __
> 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 
> 
> 
> 
> 
> -- 
> May The Force of OpenStack Be With You, 
> 
> Rico Lin
> Chief OpenStack Technologist, inwinSTACK
> irc: ricolin
> 
> __
> 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] [openstack-manuals] What the status of DocImpact

[Doug Hellmann]

Excerpts from Matt Riedemann's message of 2016-04-24 15:54:03 -0500:
> On 4/24/2016 8:03 AM, ZhiQiang Fan wrote:
> > but Document Team has so beautiful tables, and so convenient tools
> > , it is a huge waste of resource if we manually
> > write it to release note in each project.
> >
> > So I want to figure out what have happened to prevent Document Team
> > continuing previous workflow.
> >
> > Thanks
> >
> > On Sun, Apr 24, 2016 at 8:54 PM, Doug Hellmann  > > wrote:
> >
> > Excerpts from ZhiQiang Fan's message of 2016-04-24 08:00:10 +0800:
> > > Hi Doc Team,
> > >
> > > I want to know the recent status of DocImpact tag, is it
> > deprecated for
> > > config option changes now? If it's true, then what the workflow
> > for config
> > > reference now, any hint or link?
> > >
> > > Previously, when a patch has impact to document, including config
> > option
> > > changes, I usually ask contributors to add a DocImpact, hence
> > there will be
> > > a bug track the document issue.
> > >
> > > Recently, a patch lands in Ceilometer which adds two new options, and
> > > Ceilometer receives the auto created document bug. However, when I
> > submit a
> > > patch to openstack-manuals to fix it, I was told by a core that
> > such change
> > > is not needed any more, I searched latest merged patch in
> > openstack-manuals
> > > and found what he said is true, but still don't know why and what
> > action I
> > > should follow in Ceilometer/Aodh projects
> > >
> > > Thank you very much!
> > >
> > > ZhiQiang Fan
> >
> > I recommend at a minimum including a release note using reno in the
> > patch changing any configuration options (adding, deprecating, changing
> > defaults, etc.).
> >
> > Doug
> >
> >
> 
> The point of adding a release note for new config options is because 
> they are generally added for a feature, so the release note advertises 
> that feature and how to use it (with the config option).
> 
> The point in adding a release note when deprecating and removing config 
> options is because of the upgrade impact (another tag that would go 
> unnoticed). Deployers are using the release notes when doing upgrades, 
> so they need to be aware of these things without having to diff the 
> massive config options pages between releases and try to sort everything 
> out.
> 

Great explanation, Matt!

There are also far far more contributors making changes that need to be
documented than we have on the documentation team, so we can't reasonably
expect them to keep up. Decentralizing the documentation effort by doing
the work in each project as changes are made ensures that we have good
release notes at each milestone and release, without overburdening any
one person or group with that work.

That said, release notes don't have to be exhaustive documentation for a
new feature or change. They should describe the change briefly, mention
configuration options that are added or removed, and refer to more
extensive documentation for more detail.

Doug

__
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] Distributed Database

[Jay Pipes]

On 04/25/2016 03:06 AM, Chris Dent wrote:

On Mon, 25 Apr 2016, Clint Byrum wrote:


RPC being a different animal, we're, frankly, abusing RabbitMQ in silly
ways. There are a _massive_ pile of simpler things just waiting to
be tried:


Yes, very much yes. I think much of the rest of the discussions about
improving the architecture of OpenStack are moot until we address
the Rabbit abuse.


Yes some more. The above is the fundamental issue with our messaging 
infrastructure that needs to be addressed.


-jay

__
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][live migration] Feature exposure

[Timofei Durakov]

Hello,

Last week I started thread [1] on openstack-operators to ask Openstack
users about the way to expose features for live-migrations.

So here are results:

*16,7%* - All this features should work under the hood and I don't want to
enable them manually over Nova API
*33,3%* - There should be some abstraction,which allows to decide
Instance importance for me
*33,3%* - I want to get ability to specify all this features for live
migration over NovaAPI
*16,7%* - Other

Timofey

[1] -
http://lists.openstack.org/pipermail/openstack-operators/2016-April/010203.html
__
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][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

[Jeffrey Zhang]

FYI, in the current implementation, a single image seems
big, around 300MB - 1G. But when push all the image to
the registry service, you will find that the total size
of the images is just 2GB. When distribute the image, It
just takes less 30s to transfer images( 2GB / 100MB/s < 30s ).

This is what the Steve said above. Kolla leverage the docker
parent image and the total size of the images is smaller than
you think.


On Mon, Apr 25, 2016 at 4:49 PM, Fox, Kevin M  wrote:

> I really hadnt thought about distro deps for non containers leaking into
> containers like nova->libvirt. What about making a kolla-container rpm that
> provides a virtual libvirt package and anything else not actually needed in
> the container?
>
> Thanks,
> Kevin
>
> --
> *From:* Steven Dake (stdake)
> *Sent:* Monday, April 25, 2016 1:01:16 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [kolla][kubernetes] Mirantis participation
> in kolla-mesos project and shift towards Kubernetes
>
> Tomasz,
> Response inline.
>
> On 4/25/16, 12:32 AM, "Tomasz Pa"  wrote:
>
> >On Mon, Apr 25, 2016 at 5:51 AM, Jeffrey Zhang 
> >wrote:
> >>
> >> I do not think this is the issue of Kolla. It is a issue of Docker
> >> images. All the docker images has such issue. This should be solved
> >> in the docker side.
> >>
> >
> >It's a kolla issue and they way project build images. Calling yum
> >install in Dockerfile is not the best idea (you endup with multiple
> >dependent packages put into the single image layer). Having some good
> >DSL would mean that you can place each package into separate image
> >layer (ie: RUN rpm -i ./python-nova-.rpm) and take advantage of
> >that during build (reusing cached layers).
>
> In the case were there are a common set of packages that end up in every
> layer, Kolla has optimized for the general build and use case by
> extracting the commonly used dependencies into a base image used by all
> containers.
>
> Reference from binary:
> https://github.com/openstack/kolla/blob/master/docker/openstack-base/Docker
> file.j2#L129
>
>
> Reference from source:
> https://github.com/openstack/kolla/blob/master/docker/openstack-base/Docker
> file.j2#L320
>
>
> Kolla developers essentially count the number of times that requests
> package would be installed in a dependent container, and if it reaches a
> threshold, Kolla installs it in a parent image of every openstack-service
> container.
>
> I agree it is possible to end up with multiple same dependencies in
> different containers, which is why we have this openstack-base image in
> the first place - to serve as a MACRO optimization to solve the very
> problem you point out.
>
> I fail to see how a DSL would improve on this master openstack-base image.
>
> My build times on my gear are 14 minutes for 115+ containers.  I do have
> Intel 750 NVME SSD and gige internet, however, even folks with slower
> storage and networking report 30-35 minute build times which are in the
> window of "not too long to do once in awhile".
>
> But I'll grant you, I personally think every time I rebuild all my images
> on my host I could be doing something better with my time.  I just don't
> think a DSL would help speed up build times as you have claimed, except
> for the one-off case of nova (because of its dependency on libvirt).
>
> What I'd hate to see happen is a DSL invented and used in Kolla that
> specifies each specific dependency to install for binary-packaging.  That
> is what rpm/deb is designed to handle.
>
> For the case of source builds, requirements.txt serves the same purpose.
>
> Regards
> -steve
>
> >
> >
> >--
> >Tomasz Paszkowski
> >SS7, Asterisk, SAN, Datacenter, Cloud Computing
> >+48500166299
> >
> >__
> >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
>
>


-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [Fuel][plugins] Changing role regex from '*' to ['/.*/'] breaks MOS compatibility

[Ilya Kutukov]

You are welcome!

On Sat, Apr 23, 2016 at 11:00 AM, Guillaume Thouvenin 
wrote:

> Yes this patch fixes the issue.
> Thanks Ilya.
>
> On Fri, Apr 22, 2016 at 4:53 PM, Ilya Kutukov 
> wrote:
>
>> Hello!
>>
>> I think your problem is related to the:
>> https://bugs.launchpad.net/fuel/+bug/1570846
>>
>> Fix to stable/mitaka was commited 20/04/2016
>> https://review.openstack.org/#/c/307658/
>>
>> Could you, please, try to apply this patch and reply does it help or not.
>>
>> On Fri, Apr 22, 2016 at 5:40 PM, Guillaume Thouvenin 
>> wrote:
>>
>>> Hello,
>>>
>>> deployment_tasks.yaml for the fuel-plugin-lma-collector plugin has this
>>> task definition:
>>>
>>> - id: lma-aggregator
>>>   type: puppet
>>>   version: 2.0.0
>>>   requires: [lma-base]
>>>   required_for: [post_deployment_end]
>>>   role: '*'
>>>   parameters:
>>> puppet_manifest: puppet/manifests/aggregator.pp
>>> puppet_modules: puppet/modules:/etc/puppet/modules
>>> timeout: 600
>>>
>>> It works well with MOS 8. Unfortunately it doesn't work anymore with MOS
>>> 9: the task doesn't appear in the deployment graph. The regression seems to
>>> be introduced by the computable-task-fields-yaql feature [1].
>>>
>>> We could use "roles: ['/.*/']" instead of "role: '*' " but then the task
>>> is skipped when using MOS 8. We also tried to declare both "roles" and
>>> "role" but again this doesn't work.
>>>
>>> How can we ensure that the same version of the plugin can be deployed on
>>> both versions of MOS? Obviously maintaining one Git branch per MOS release
>>> is not an option.
>>>
>>> [1] https://review.openstack.org/#/c/296414/
>>>
>>> Regards,
>>> Guillaume
>>>
>>>
>>>
>>> __
>>> 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

Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

[Fox, Kevin M]

I really hadnt thought about distro deps for non containers leaking into 
containers like nova->libvirt. What about making a kolla-container rpm that 
provides a virtual libvirt package and anything else not actually needed in the 
container?

Thanks,
Kevin


From: Steven Dake (stdake)
Sent: Monday, April 25, 2016 1:01:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla][kubernetes] Mirantis participation in 
kolla-mesos project and shift towards Kubernetes

Tomasz,
Response inline.

On 4/25/16, 12:32 AM, "Tomasz Pa"  wrote:

>On Mon, Apr 25, 2016 at 5:51 AM, Jeffrey Zhang 
>wrote:
>>
>> I do not think this is the issue of Kolla. It is a issue of Docker
>> images. All the docker images has such issue. This should be solved
>> in the docker side.
>>
>
>It's a kolla issue and they way project build images. Calling yum
>install in Dockerfile is not the best idea (you endup with multiple
>dependent packages put into the single image layer). Having some good
>DSL would mean that you can place each package into separate image
>layer (ie: RUN rpm -i ./python-nova-.rpm) and take advantage of
>that during build (reusing cached layers).

In the case were there are a common set of packages that end up in every
layer, Kolla has optimized for the general build and use case by
extracting the commonly used dependencies into a base image used by all
containers.

Reference from binary:
https://github.com/openstack/kolla/blob/master/docker/openstack-base/Docker
file.j2#L129


Reference from source:
https://github.com/openstack/kolla/blob/master/docker/openstack-base/Docker
file.j2#L320


Kolla developers essentially count the number of times that requests
package would be installed in a dependent container, and if it reaches a
threshold, Kolla installs it in a parent image of every openstack-service
container.

I agree it is possible to end up with multiple same dependencies in
different containers, which is why we have this openstack-base image in
the first place - to serve as a MACRO optimization to solve the very
problem you point out.

I fail to see how a DSL would improve on this master openstack-base image.

My build times on my gear are 14 minutes for 115+ containers.  I do have
Intel 750 NVME SSD and gige internet, however, even folks with slower
storage and networking report 30-35 minute build times which are in the
window of "not too long to do once in awhile".

But I'll grant you, I personally think every time I rebuild all my images
on my host I could be doing something better with my time.  I just don't
think a DSL would help speed up build times as you have claimed, except
for the one-off case of nova (because of its dependency on libvirt).

What I'd hate to see happen is a DSL invented and used in Kolla that
specifies each specific dependency to install for binary-packaging.  That
is what rpm/deb is designed to handle.

For the case of source builds, requirements.txt serves the same purpose.

Regards
-steve

>
>
>--
>Tomasz Paszkowski
>SS7, Asterisk, SAN, Datacenter, Cloud Computing
>+48500166299
>
>__
>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] Distributed Database

[Chris Dent]

On Mon, 25 Apr 2016, Clint Byrum wrote:


RPC being a different animal, we're, frankly, abusing RabbitMQ in silly
ways. There are a _massive_ pile of simpler things just waiting to
be tried:


Yes, very much yes. I think much of the rest of the discussions about
improving the architecture of OpenStack are moot until we address
the Rabbit abuse.

--
Chris Dent   (╯°□°)╯︵┻━┻http://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] [kolla][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

[Steven Dake (stdake)]

Tomasz,
Response inline.

On 4/25/16, 12:32 AM, "Tomasz Pa"  wrote:

>On Mon, Apr 25, 2016 at 5:51 AM, Jeffrey Zhang 
>wrote:
>>
>> I do not think this is the issue of Kolla. It is a issue of Docker
>> images. All the docker images has such issue. This should be solved
>> in the docker side.
>>
>
>It's a kolla issue and they way project build images. Calling yum
>install in Dockerfile is not the best idea (you endup with multiple
>dependent packages put into the single image layer). Having some good
>DSL would mean that you can place each package into separate image
>layer (ie: RUN rpm -i ./python-nova-.rpm) and take advantage of
>that during build (reusing cached layers).

In the case were there are a common set of packages that end up in every
layer, Kolla has optimized for the general build and use case by
extracting the commonly used dependencies into a base image used by all
containers.

Reference from binary:
https://github.com/openstack/kolla/blob/master/docker/openstack-base/Docker
file.j2#L129


Reference from source:
https://github.com/openstack/kolla/blob/master/docker/openstack-base/Docker
file.j2#L320


Kolla developers essentially count the number of times that requests
package would be installed in a dependent container, and if it reaches a
threshold, Kolla installs it in a parent image of every openstack-service
container.

I agree it is possible to end up with multiple same dependencies in
different containers, which is why we have this openstack-base image in
the first place - to serve as a MACRO optimization to solve the very
problem you point out.

I fail to see how a DSL would improve on this master openstack-base image.

My build times on my gear are 14 minutes for 115+ containers.  I do have
Intel 750 NVME SSD and gige internet, however, even folks with slower
storage and networking report 30-35 minute build times which are in the
window of "not too long to do once in awhile".

But I'll grant you, I personally think every time I rebuild all my images
on my host I could be doing something better with my time.  I just don't
think a DSL would help speed up build times as you have claimed, except
for the one-off case of nova (because of its dependency on libvirt).

What I'd hate to see happen is a DSL invented and used in Kolla that
specifies each specific dependency to install for binary-packaging.  That
is what rpm/deb is designed to handle.

For the case of source builds, requirements.txt serves the same purpose.

Regards
-steve

>
>
>-- 
>Tomasz Paszkowski
>SS7, Asterisk, SAN, Datacenter, Cloud Computing
>+48500166299
>
>__
>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] [Magnum] Magnum supports 2 Nova flavor to provision minion nodes

[Duan, Li-Gong (Gary, HPServers-Core-OE-PSC)]

Hi Ricardo,

This is really good suggestion. I'd like to see whether we can use 
"foreach"/"repeat" in ResourceGroup in Heat.

Regards,
Gary Duan

-Original Message-
From: Ricardo Rocha [mailto:rocha.po...@gmail.com] 
Sent: Thursday, April 21, 2016 3:49 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to 
provision minion nodes

Hi Hongbin.

On Wed, Apr 20, 2016 at 8:13 PM, Hongbin Lu  wrote:
>
>
>
>
> From: Duan, Li-Gong (Gary, HPServers-Core-OE-PSC) 
> [mailto:li-gong.d...@hpe.com]
> Sent: April-20-16 3:39 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Magnum] Magnum supports 2 Nova flavor to 
> provision minion nodes
>
>
>
> Hi Folks,
>
>
>
> We are considering whether Magnum can supports 2 Nova flavors to 
> provision Kubernetes and other COE minion nodes.
>
> This requirement comes from the below use cases:
>
> -  There are 2 kind of baremetal machines in customer site: one is
> legacy machines which doesn’t support UEFI secure boot and others are 
> new machines which support UEFI secure boot. User want to use Magnum 
> to provisions a Magnum bay of Kubernetes from these 2 kind of 
> baremetal machines and for the machines supporting secure boot, user 
> wants to use UEFI secure boot to boot them up. And 2 Kubernetes 
> label(secure-booted and
> non-secure-booted) are created and User can deploy their 
> data-senstive/cirtical workload/containers/pods on the baremetal 
> machines which are secure-booted.
>
>
>
> This requirement requires Magnum to supports 2 Nova flavors(one is
> “extra_spec: secure_boot=True” and the other doesn’t specify it) based 
> on the Ironic 
> feature(https://specs.openstack.org/openstack/ironic-specs/specs/kilo-
> implemented/uefi-secure-boot.html
> ).
>
>
>
> Could you kindly give me some comments on these requirement or whether 
> it is reasonable from your point? If you agree, we can write design 
> spec and implement this feature?
>
>
>
> I think the requirement is reasonable, but I would like to solve the 
> problem in a generic way. In particular, there could be another user 
> who might ask for N nova flavors to provision COE nodes in the future. 
> A challenge to support N groups of Nova instances is how to express 
> arbitrary number of resource groups (with different flavors) in a Heat 
> template (Magnum uses Heat template to provision COE clusters). Heat 
> doesn’t seem to support the logic of looping from 1 to N. There could 
> be other challenges/complexities along the way. If the proposed design 
> can address all the challenges and the implementation is clean, I am 
> OK to add support for this feature. Thoughts from others?

This looks similar to the way we looked at passing a list of availability 
zones. Mathieu asked and got a good answer:
http://lists.openstack.org/pipermail/openstack-dev/2016-March/088175.html

Something similar can probably be used to pass multiple flavors? Just in case 
it helps.

Cheers,
  Ricardo

>
>
>
> Regards,
>
> 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
__
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] [Fuel] Fuel 9.0 is released

[Guo, Ruijing]

Can we support alternative way to download ISO since p2p may be prevented in 
some company IT?

Thanks,
-Ruijing

From: Vladimir Kozhukalov [mailto:vkozhuka...@mirantis.com]
Sent: Thursday, April 21, 2016 10:52 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [Fuel] Fuel 9.0 is released


Dear all,


I am glad to announce Mitaka release of Fuel (a.k.a Fuel 9.0) - deployment

and lifecycle management tool for OpenStack.


This release introduces support for OpenStack Mitaka and adds

a number of new features and enhancements.


Some highlights:
- Support lifecycle management operations (a.k.a ‘day 2’ operations).
Now cluster settings tab on UI is unlocked after deployment
(cluster configuration could be changed). [1]
- Support of custom deployment graphs. Default deployment graph
could be overridden either by plugins or by a user. [2]
- Support of DPDK capabilities [3]
- Support of Huge Pages capabilities [4]
- Support of CPU pinning (NUMA) capabilities [5]
- Support of QoS capabilities [6]
- Support of SR-IOV capabilities [7]
- Support of multipath devices [8]
- Support of deployment using UCA packages [9]

Please be aware that it is not intended for production use and

there are still about 90 known High bugs [10]. We are planning

to address them all in Fuel 9.0.1 release which is scheduled

for late June [11].


We are looking forward to your feedback.
Great work, Fuel team. Thanks to everyone.


[1] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/unlock-settings-tab.rst

[2] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/execute-custom-graph.rst

[1] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/support-dpdk.rst

[3] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/execute-custom-graph.rst
[4] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/support-hugepages.rst
[5] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/support-numa-cpu-pinning.rst
[6] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/support-qos.rst
[7] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/support-sriov.rst
[8] 
https://github.com/openstack/fuel-specs/blob/master/specs/9.0/fc-multipath-disks.rst
[9] https://blueprints.launchpad.net/fuel/+spec/deploy-with-uca-packages

[10] https://goo.gl/qXfrhQ

[11] https://wiki.openstack.org/wiki/Fuel/9.0_Release_Schedule


Learn more about Fuel:
https://wiki.openstack.org/wiki/Fuel

How we work:
https://wiki.openstack.org/wiki/Fuel/How_to_contribute

Specs for features in 9.0 and other Fuel releases:
http://specs.openstack.org/openstack/fuel-specs/

ISO image:
http://seed.fuel-infra.org/fuelweb-community-release/fuel-community-9.0.iso.torrent

Test results of the release build:
https://ci.fuel-infra.org/job/9.0-community.test_all/61/

Documentation:
http://docs.openstack.org/developer/fuel-docs/


RPM packages:
http://mirror.fuel-infra.org/mos-repos/centos/mos9.0-centos7/

DEB packages:
http://mirror.fuel-infra.org/mos-repos/ubuntu/9.0/
Vladimir Kozhukalov
__
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][kubernetes] Mirantis participation in kolla-mesos project and shift towards Kubernetes

[Steven Dake (stdake)]

On 4/24/16, 10:05 PM, "Tomasz Pa"  wrote:

>On Sat, Apr 23, 2016 at 2:27 AM, Steven Dake (stdake) 
>wrote:
>>
>> Trying to understand the issue here, do you believe the current jinja2
>> Dockerfiles are not readable?  I'm pretty sure my 11 and 13 year old
>> children which are just learning programming already understand
>>conditionals
>> and variables.  A full-blown DSL for describing container contents
>>seems out
>> of the domain of Kolla's mission, although I'd never say no if someone
>> wanted to give a crack at implementing one.
>
>Kolla images are simply to big and not properly layered. What it means
>that if you today want to upgrade one of the packages: ie: python-nova
>(assuming images are build from RPMs) you're upgrading whole layer
>which contains all it's dependencies added by yum. So at the end
>simple 12MB upgrades turns to be 120MB (right now this is the size of
>the kolla image layer which contains python-nova).
>
>Having some proper DSL for describing container content would mean
>that we can have each package deployed within it's own image layer.
>This would definitely speed up upgrades and would ensure better layer
>sharing between multiple images.
>
>Cheers

I disagree with your assertion.  You are gaming your data to provide the
worst possible container (nova) because the RPMs pull in libvirt.  Kolla
has no control over how Red Hat choses to package RDO, and at this time
they choose to package libvirt as a dependency thereof.  Obviously it
would be more optimal in a proper container system not to include libvirt
in the dependencies installed with Nova.  If you really want that, use
from source installs.  Then you could shave 1 minute off your upgrade time
of a 64 node cluster.

A DSL does not solve this problem unless the DSL contains every dependency
to install (from binary).  I don't see this as maintainable.

But lets talk about how real containers affect outcomes of deployment and
upgrade times without the usage of a DSL.

A centos deployment of Kolla was measured at 25 minutes on a 64 node OSIC
cluster.  An upgrade was measured at 12 minutes.  This is 2-10x faster
then other deployment systems at either upgrade or deployment of the same
cluster size.

Essentially I think you suggest a micro-optimization for nova in the
one-off case of RPM installations, which is taking a sledge hammer to a
needle.  From source doesn't suffer from this problem and no other
containers beyond Nova suffer from this problem either.

But just to put real numbers on this, a deployment of Kolla was measured
at 25 minutes on an OSIC 64 node cluster.

An upgrade was measured at 12 minutes for that same 64 node cluster.

Creating a DSL to optimize for the nova imports libvirt dependency issue
is super-overkill and is a super micro-optimization.

Please provide a better and more relevant example.

Just as a conclusion, deploying each dependency in a separate layer is an
absolutely terrible idea.  Docker performance atleast is negatively
affected by large layer counts, and aufs has a limit of 42 layers, so your
idea is not viable asp resented.

Cheers

>
>__
>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] Distributed Database

[Clint Byrum]

Excerpts from Andrew Laski's message of 2016-04-22 14:32:59 -0700:
> 
> On Fri, Apr 22, 2016, at 04:27 PM, Ed Leafe wrote:
> > OK, so I know that Friday afternoons are usually the worst times to
> > write a blog post and start an email discussion, and that the Friday
> > immediately before a Summit is the absolute worst, but I did it anyway.
> > 
> > http://blog.leafe.com/index.php/2016/04/22/distributed_data_nova/
> > 
> > Summary: we are creating way too much complexity by trying to make Nova
> > handle things that are best handled by a distributed database. The
> > recent split of the Nova DB into an API database and separate cell
> > databases is the glaring example of going down the wrong road.
> > 
> > Anyway, read it on your flight (or, in my case, drive) to Austin, and
> > feel free to pull me aside to explain just how wrong I am. ;-)
> 
> I agree with a lot of what Monty wrote in his response. And agree that
> given a greenfield there are much better approaches that could be taken
> rather than partitioning the database.
> 
> However I do want to point out that cells v2 is not just about dealing
> with scale in the database. The message queue is another consideration,
> and as far as I know there is not an analog to the "distributed
> database" option available for the persistence layer.
> 

It's not even scale, it is failure domain isolation. I'm pretty
confident I can back 1000 busy compute nodes with a single 32 core 128GB
RabbitMQ. But, to do so is basically pure madness because of the failover
costs. Having 10x8 core RabbitMQ servers, as Cells v2 wants to do, means
the disruption caused by disrupting any one of them should be able to be
contained to 1/10th of the instances running. However, that assumes the
complexity of the implementation won't leak out to the unaffected servers.

Anyway, for messaging, part of the problem is until somewhat recently,
we thought RPC and Notifications were the same thing. They're VASTLY
different. For things like notifications, you don't need to look beyond
Apache Kafka to see that scale-out solutions exist. Also, if you
actually separate these two, you'll find that a single tiny RabbitMQ
cluster can handle the notifications without breaking a tiny sweat,
because it uses RabbitMQ for what it was actually designed for (Lots of
messages, few topics).

RPC being a different animal, we're, frankly, abusing RabbitMQ in silly
ways. There are a _massive_ pile of simpler things just waiting to
be tried:

- 0MQ - There's this fear of change and a bit of chicken/egg preventing
  this from becoming the default choice for RPC any time soon. I for one
  want to look into it, but keep getting side tracked because RMQ is
  "good enough" for now, and the default.
  
- Direct HTTP for RPC - I've always wondered why we don't do this for
  RPC. Same basic idea as 0MQ, but even more familiar to all of us.
  
- Thrift

- gRPC/protobuf

The basic theme for RPC is simple: just send the messages to the
services directly.

> Additionally with v1 we found that deployers have enjoyed being able to
> group their hardware with cells. Baremetal goes in this cell, SSD filled
> computes over here, and spinning disks over there. And beyond that
> there's the ability to create a cell, fill it with hardware, and then
> test it without plugging it up to the production API. Cells provides an
> entry point for poking at things that isn't available without it.
> 
> I don't want to get too sidetracked on talking about cells. I just
> wanted to point out that cells v2 did not come to fruition due to a fear
> of distributed databases.
> 

I'd love for the feature described to be separate from scaling. It's a
great feature, but it's just a happy accident that it helps with scale,
and would work just as well if we called it "host aggregates" and actually
made host aggregates work well.

__
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] Error runnig py27

[Khayam Gondal]

thanks

On Tue, Apr 19, 2016 at 7:51 AM, joehuang  wrote:

> Hello, Khayam,
>
>
>
> You can write the test case for the exception like :
> http://paste.openstack.org/show/494530/
>
>
>
> Best Regards
>
> Chaoyi Huang ( Joe Huang )
>
>
>
> *From:* Khayam Gondal [mailto:khayam.gon...@gmail.com]
> *Sent:* Monday, April 18, 2016 8:22 PM
>
> *To:* joehuang
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> Zhiyuan Cai
> *Subject:* Re: [Tricircle] Error runnig py27
>
>
>
> Sorry, email went to spam. Just saw it.
>
> Following is link
>
> http://paste.openstack.org/show/494403/
>
>
>
> On Mon, Apr 18, 2016 at 8:41 AM, joehuang  wrote:
>
> Hi, Khayam,
>
>
>
> Could you paste your whole file for test cases and the source code to be
> tested in the http://paste.openstack.org/ seperatly.
>
>
>
> Please share the links, so that to find out what happened.
>
>
>
> Best Regards
>
> Chaoyi Huang ( Joe Huang )
>
>
>
> *From:* Khayam Gondal [mailto:khayam.gon...@gmail.com]
> *Sent:* Thursday, April 14, 2016 5:30 PM
> *To:* joehuang
> *Cc:* OpenStack Development Mailing List (not for usage questions);
> Zhiyuan Cai
> *Subject:* Re: [Tricircle] Error runnig py27
>
>
>
> Hi joehuang,
>
> by removing self it is showing following error.
>
>
>
>   File
> "/home/khayam/tricircle/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
> line 1206, in _importer
>
> thing = __import __ (import_path)
>
> Import Error: No module named app
>
> Ran 135 tests in 2.994s (+ 0.940s)
>
>
>
>
>
> On Thu, Apr 14, 2016 at 5:53 AM, joehuang  wrote:
>
> Hi, Khayam,
>
>
>
> @mock.patch(*'self.app.post_json'*)
>
>
>
> No “self.” needed.
>
>
>
> Best Regards
>
> Chaoyi Huang ( Joe Huang )
>
>
>
> *From:* Khayam Gondal [mailto:khayam.gon...@gmail.com]
> *Sent:* Wednesday, April 13, 2016 2:50 PM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Cc:* joehuang; Zhiyuan Cai
> *Subject:* [Tricircle] Error runnig py27
>
>
>
> Hi I am writing a test for exception . Following is my testing function.
>
> @mock.patch(*'self.app.post_json'*)
> *def *test_post_exp(self, mock_get, mock_http_error_handler):
>
> mock_response = mock.Mock()
> mock_response.raise_for_status.side_effect = db_exc.DBDuplicateEntry
> mock_get.return_value = mock_response
> mock_http_error_handler.side_effect = db_exc.DBDuplicateEntry
> *with *self.assertRaise(db_exc.DBDuplicateEntry):
> self.app.post_json(
> *'/v1.0/pods'*,
> dict(pod=None),
> expect_errors=True)
>
> But when I run tox -epy27 it shows:
>
>  * File 
> "/home/khayam/tricircle/.tox/py27/local/lib/python2.7/site-packages/mock/mock.py",
>  line 1206, in _importer*
>
> *thing = __import__(import_path)*
>
> *ImportError: No module named self*
>
> Can someone guide me whats wrong here. I already had installed latest version 
> of mock, python-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