Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Brandon Logan]

Yeah that’s a good point.  Thanks!

From: Eugene Nikanorov mailto:enikano...@mirantis.com>>
Reply-To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 15, 2014 at 10:38 PM
To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Brandon,

It's allowed right now just per API. It's up to a backend to decide the status 
of a node in case some monitors find it dead.

Thanks,
Eugene.



On Fri, May 16, 2014 at 4:41 AM, Brandon Logan 
mailto:brandon.lo...@rackspace.com>> wrote:
I have concerns about multiple health monitors on the same pool.  Is this 
always going to be the same type of health monitor?  There’s also ambiguity in 
the case where one health monitor fails and another doesn’t.  Is it an AND or 
OR that determines whether the member is down or not?

Thanks,
Brandon Logan

From: Eugene Nikanorov mailto:enikano...@mirantis.com>>
Reply-To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 15, 2014 at 9:55 AM
To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>

Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Vijay,

Pools-monitors are still many to many, if it's not so on the picture - we'll 
fix that.
I brought this up as an example of how we dealt with m:n via API.

Thanks,
Eugene.


On Thu, May 15, 2014 at 6:43 PM, Vijay Venkatachalam 
mailto:vijay.venkatacha...@citrix.com>> wrote:
Thanks for the clarification. Eugene.

A tangential point since you brought healthmon and pool.

There will be an additional entity called ‘PoolMonitorAssociation’ which 
results in a many to many relationship between pool and monitors. Right?

Now, the model is indicating a pool can have only one monitor. So a minor 
correction is required to indicate the many to many relationship via 
PoolMonitorAssociation.

Thanks,
Vijay V.


From: Eugene Nikanorov 
[mailto:enikano...@mirantis.com]
Sent: Thursday, May 15, 2014 7:36 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Hi Vijay,


When you say API is not available, it means this should not be considered like 
a resource/entity. Correct?

But then, there would be API like a bind API, that accepts loadbalancer_id & 
listener_id,  which creates this object.
And also, there would be an API that will be used to list the listeners of a 
LoadBalancer.

Right?
Right, that's the same as health monitors and pools work right now: there are 
separate REST action to associate healthmon to a pool


Thanks,
Eugene.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Ironic] UEFI boot support in ironic deploy drivers

[Faizan Barmawer]

Hi Folks,

I am currently working on the following blueprints on UEFI boot support for
ironic deploy drivers.

https://blueprints.launchpad.net/ironic/+spec/uefi-boot-for-ironic
https://blueprints.launchpad.net/ironic/+spec/uefi-gpt-support

I have updated the proposed changes for in the below etherpad.
https://etherpad.openstack.org/p/IronicUEFISupport

I request you to review this and give your comments and suggestions.

Regards,
Faizan
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS]LBaaS 2nd Session etherpad

[Samuel Bercovici]

Hi Everyone,

https://etherpad.openstack.org/p/neutron-lbaas-ssl-l7

Feel free to modify and update, please make sure you use your name so we will 
know who have added the modification.

Regards,
-Sam.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Eugene Nikanorov]

Brandon,

It's allowed right now just per API. It's up to a backend to decide the
status of a node in case some monitors find it dead.

Thanks,
Eugene.



On Fri, May 16, 2014 at 4:41 AM, Brandon Logan
wrote:

>  I have concerns about multiple health monitors on the same pool.  Is
> this always going to be the same type of health monitor?  There’s also
> ambiguity in the case where one health monitor fails and another doesn’t.
>  Is it an AND or OR that determines whether the member is down or not?
>
>  Thanks,
> Brandon Logan
>
>   From: Eugene Nikanorov 
> Reply-To: "openstack-dev@lists.openstack.org" <
> openstack-dev@lists.openstack.org>
> Date: Thursday, May 15, 2014 at 9:55 AM
> To: "openstack-dev@lists.openstack.org"  >
>
> Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?
>
>   Vijay,
>
>  Pools-monitors are still many to many, if it's not so on the picture -
> we'll fix that.
> I brought this up as an example of how we dealt with m:n via API.
>
>  Thanks,
> Eugene.
>
>
> On Thu, May 15, 2014 at 6:43 PM, Vijay Venkatachalam <
> vijay.venkatacha...@citrix.com> wrote:
>
>>  Thanks for the clarification. Eugene.
>>
>>
>>
>> A tangential point since you brought healthmon and pool.
>>
>>
>>
>> There will be an additional entity called ‘PoolMonitorAssociation’ which
>> results in a many to many relationship between pool and monitors. Right?
>>
>>
>>
>> Now, the model is indicating a pool can have only one monitor. So a minor
>> correction is required to indicate the many to many relationship via
>> PoolMonitorAssociation.
>>
>>
>>
>> Thanks,
>>
>> Vijay V.
>>
>>
>>
>>
>>
>> *From:* Eugene Nikanorov [mailto:enikano...@mirantis.com]
>> *Sent:* Thursday, May 15, 2014 7:36 PM
>>
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?
>>
>>
>>
>> Hi Vijay,
>>
>>
>>
>>
>> When you say API is not available, it means this should not be considered
>> like a resource/entity. Correct?
>>
>>
>>
>> But then, there would be API like a bind API, that accepts
>> loadbalancer_id & listener_id,  which creates this object.
>>
>> And also, there would be an API that will be used to list the listeners
>> of a LoadBalancer.
>>
>>
>>
>> Right?
>>
>>  Right, that's the same as health monitors and pools work right now:
>> there are separate REST action to associate healthmon to a pool
>>
>>
>>
>>
>>
>> Thanks,
>>
>> Eugene.
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Heat SoftwareConfig and SoftwareDevelopment

[Thomas Spatzier]

Excerpts from Lingxian Kong's message on 15/05/2014 22:51:33:
> From: Lingxian Kong 
> To: "OpenStack Development Mailing List (not for usage questions)"
> 
> Date: 15/05/2014 22:53
> Subject: Re: [openstack-dev] Heat SoftwareConfig and SoftwareDevelopment
>

>
> Do you know any information about examples or tutorials when using
> SoftwareConfig and SoftwareDeployment? I found it's a little difficult
> to understand for me.

Unfortunately, we do not have any good documentation (or any documentation
at all) on this right now. I was planning to start some, but did not get to
it so far. For now, you could look at some examples in the heat-templates
repository at

https://github.com/openstack/heat-templates/tree/master/hot/software-config/example-templates

Especially in

https://github.com/openstack/heat-templates/tree/master/hot/software-config/example-templates/wordpress

you can see the WordPress example that has been widely used in Heat
samples, but making use of SoftwareConfig and SoftwareDeployment.

Regards,
Thomas

>
> I know there are already some wikis, but not sufficient for me, :(
>
> Thanks!
>
> --
> -
> Lingxian Kong___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Heat SoftwareConfig and SoftwareDevelopment

[Lingxian Kong]

2014-05-14 11:51 GMT+08:00 Qiming Teng :

> Icehouse version should be okay. You may want to check the readme files
> and the sample templates.  In general, you need hooks specific to your
> configuration tool (shell script in this case) installed in your VM.
>
>
​hi ​Qiming:

Do you know any information about examples or tutorials when using
SoftwareConfig and SoftwareDeployment? I found it's a little difficult
to understand for me.

I know there are already some wikis, but not sufficient for me, :(

Thanks!


-- 
*-*
*Lingxian Kong*
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Mistral][TaskFlow] Integration plan

[Joshua Harlow]

Looks good to me,

We had a good 'meetup' in one of the breakout rooms on the second floor
(those rooms are pretty useful!)

This does seem like a good step toward making both groups successful and
from the discussion I think we have a decent vision of how this can/could
work out in the future and moving forward (and even some other neat ideas
on related areas were also discovered/discussed, which is pretty cool).

I'll writeup some more these as TF blueprints next week and we can
continue there (iterating on them and getting some code
produced/adjusted/refactored). The timeline maybe we should continue
thinking about as I'm still sure on the 'final' date but I agree with the
get started now and we can start to 'approximate' what the date would be
as we get a better 'feeling' for it (K seems like a good estimate).

Another idea:

The bi-weekly meetings between teams/individuals/other on IRC seemed like
a good idea (to at least sync and discuss ideas and such), maybe we should
continue those. What do u guys think?

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

Date: Thursday, May 15, 2014 at 1:06 PM
To: "OpenStack Development Mailing List (not for usage questions)"

Subject: [openstack-dev] [Mistral][TaskFlow] Integration plan

>Renat, Joshua, Dmitri and Timur discussed the integration path for
>Mistral and TaskFlow.
>Quick summary - guys please correct any mistakes or omissions:
>
>Taskflow - Mistral integration plan
>1) Mistral: define the set of workflow primitives, define correspondent
>DSL
>   - Driven by user requirements. Keep to minimal. Implement in Mistral.
>2) Taskflow: break out flow scheduler (decision maker) and persistence
>   - it'll be a low level "library" interference, Joshua has details
>   - once done, ready to re-prototype integration, iterate until happy
>3) Move the primitives to TaskFlow (both teams)
>
>4) Integrate TaskFlow into Mistral (replace Mistral workflow engine with
>TaskFlow engine)
>
>Once integration complete, Mistral DSL will continue to work, all
>TaskFlow and Mistral workflows will be interchangeable, the code reused.
>
>DZ. 
>
>PS. When do we do it? We didn't commit to a date,
>but IMO (DZ) we start now, and with some luck get integrated in K cycle.
>
>
>
>___
>OpenStack-dev mailing list
>OpenStack-dev@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] Logging exceptions and Python 3

[Joshua Harlow]

Any reason we would want to do this vs using exc_info=True?

This leaves it up to the underlying logger to dump the exception, the traceback 
and whatever else.

For example u can do.

>>> LOG.warn("Something broke at this point", exc_info=True)

From: Igor Kalnitsky mailto:ikalnit...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 15, 2014 at 2:20 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [oslo] Logging exceptions and Python 3

Hi,

> Is there a reason to log the exception as Unicode on Python 2?

Sure, why not? Some exceptions may have unicode message with non-ASCII
characters. and we obviously can't cast such exceptions with str() in
Python 2.x.


> The problem is that I don't know what is the best syntax to log exceptions.

I hate this unicode dances too, since I don't understand all nuances and
potential pitfalls. But I belive the better approach is to use unicode()
for Python 2.x and str() for Python 3.x.

Example:

LOG.error(six.text_type(e))


P.S: I've a quick look over logging implementaion, and figured out
that it has some code to dial with unicode. In few words, if we know
about exception's attributes, it's better to use it directly to log:

Example:

LOG.error(e.message)


- Igor


On Thu, May 15, 2014 at 6:29 PM, Victor Stinner 
mailto:victor.stin...@enovance.com>> wrote:
Hi,

I'm trying to define some rules to port OpenStack code to Python 3. I just
added a section in the "Port Python 2 code to Python 3" about formatting
exceptions and the logging module:
https://wiki.openstack.org/wiki/Python3#logging_module_and_format_exceptions

The problem is that I don't know what is the best syntax to log exceptions.
Some projects convert the exception to Unicode, others use str(). I also saw
six.u(str(exc)) which is wrong IMO (it can raise unicode error if the message
contains a non-ASCII character).

IMO the safest option is to use str(exc). For example, use
LOG.debug(str(exc)).

Is there a reason to log the exception as Unicode on Python 2?

Victor

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Anil Rao]

See you all there tomorrow.

Regards,
Anil

From: Vinay Yadhav [mailto:vinayyad...@gmail.com]
Sent: Thursday, May 15, 2014 12:51 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension 
in Neutron

Hi,

Booked a slot tomorrow at 9:20 AM at the neutron pod.


Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}

On Thu, May 15, 2014 at 2:50 PM, Stephen Wong 
mailto:s3w...@midokura.com>> wrote:
Hi Vinay,

I am interested. Please sign up a slot on Neutron pod for tomorrow (Friday) 
and announce the timeslot to the ML.

Thanks,
- Stephen


On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav 
mailto:vinayyad...@gmail.com>> wrote:
Hi,

I am Vinay, working with Ericsson.

I am interested in the following blueprint regarding port mirroring extension 
in neutron: https://blueprints.launchpad.net/neutron/+spec/port-mirroring

I am close to finishing an implementation for this extension in OVS plugin and 
would be submitting a neutron spec related to the blueprint soon.

I would like to know other who are also interested in introducing Port 
Mirroring extension in neutron.

It would be great if we can discuss and collaborate in development and testing 
this extension

I am currently attending the OpenStack Summit in Atlanta, so if any of you are 
interested in the blueprint, we can meet here in the summit and discuss how to 
proceed with the blueprint.

Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[shihanzhang]

Hi Vinay,
I am very happy to participate in this discussion!






在 2014-05-16 00:03:35，"Kanzhe Jiang"  写道：

Hi Vinay,


I am interested. You could sign up a slot for a Network POD discussion.


Thanks,
Kanzhe



On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav  wrote:

Hi,


I am Vinay, working with Ericsson.


I am interested in the following blueprint regarding port mirroring extension 
in neutron: https://blueprints.launchpad.net/neutron/+spec/port-mirroring


I am close to finishing an implementation for this extension in OVS plugin and 
would be submitting a neutron spec related to the blueprint soon.


I would like to know other who are also interested in introducing Port 
Mirroring extension in neutron.


It would be great if we can discuss and collaborate in development and testing 
this extension


I am currently attending the OpenStack Summit in Atlanta, so if any of you are 
interested in the blueprint, we can meet here in the summit and discuss how to 
proceed with the blueprint.


Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev







--
Kanzhe Jiang
MTS at BigSwitch___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Eichberger, German]

Hi,

I agree with Logan I am wondering if you can share a use case with multiple 
health monitors.

German

From: Brandon Logan [mailto:brandon.lo...@rackspace.com]
Sent: Thursday, May 15, 2014 5:41 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

I have concerns about multiple health monitors on the same pool.  Is this 
always going to be the same type of health monitor?  There's also ambiguity in 
the case where one health monitor fails and another doesn't.  Is it an AND or 
OR that determines whether the member is down or not?

Thanks,
Brandon Logan

From: Eugene Nikanorov mailto:enikano...@mirantis.com>>
Reply-To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 15, 2014 at 9:55 AM
To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Vijay,

Pools-monitors are still many to many, if it's not so on the picture - we'll 
fix that.
I brought this up as an example of how we dealt with m:n via API.

Thanks,
Eugene.

On Thu, May 15, 2014 at 6:43 PM, Vijay Venkatachalam 
mailto:vijay.venkatacha...@citrix.com>> wrote:
Thanks for the clarification. Eugene.

A tangential point since you brought healthmon and pool.

There will be an additional entity called 'PoolMonitorAssociation' which 
results in a many to many relationship between pool and monitors. Right?

Now, the model is indicating a pool can have only one monitor. So a minor 
correction is required to indicate the many to many relationship via 
PoolMonitorAssociation.

Thanks,
Vijay V.


From: Eugene Nikanorov 
[mailto:enikano...@mirantis.com]
Sent: Thursday, May 15, 2014 7:36 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Hi Vijay,


When you say API is not available, it means this should not be considered like 
a resource/entity. Correct?

But then, there would be API like a bind API, that accepts loadbalancer_id & 
listener_id,  which creates this object.
And also, there would be an API that will be used to list the listeners of a 
LoadBalancer.

Right?
Right, that's the same as health monitors and pools work right now: there are 
separate REST action to associate healthmon to a pool


Thanks,
Eugene.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Brandon Logan]

I have concerns about multiple health monitors on the same pool.  Is this 
always going to be the same type of health monitor?  There’s also ambiguity in 
the case where one health monitor fails and another doesn’t.  Is it an AND or 
OR that determines whether the member is down or not?

Thanks,
Brandon Logan

From: Eugene Nikanorov mailto:enikano...@mirantis.com>>
Reply-To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 15, 2014 at 9:55 AM
To: 
"openstack-dev@lists.openstack.org" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Vijay,

Pools-monitors are still many to many, if it's not so on the picture - we'll 
fix that.
I brought this up as an example of how we dealt with m:n via API.

Thanks,
Eugene.


On Thu, May 15, 2014 at 6:43 PM, Vijay Venkatachalam 
mailto:vijay.venkatacha...@citrix.com>> wrote:
Thanks for the clarification. Eugene.

A tangential point since you brought healthmon and pool.

There will be an additional entity called ‘PoolMonitorAssociation’ which 
results in a many to many relationship between pool and monitors. Right?

Now, the model is indicating a pool can have only one monitor. So a minor 
correction is required to indicate the many to many relationship via 
PoolMonitorAssociation.

Thanks,
Vijay V.


From: Eugene Nikanorov 
[mailto:enikano...@mirantis.com]
Sent: Thursday, May 15, 2014 7:36 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Hi Vijay,


When you say API is not available, it means this should not be considered like 
a resource/entity. Correct?

But then, there would be API like a bind API, that accepts loadbalancer_id & 
listener_id,  which creates this object.
And also, there would be an API that will be used to list the listeners of a 
LoadBalancer.

Right?
Right, that's the same as health monitors and pools work right now: there are 
separate REST action to associate healthmon to a pool


Thanks,
Eugene.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] Logging exceptions and Python 3

[Christian Berendt]

On 05/15/2014 11:20 PM, Igor Kalnitsky wrote:
> Example:
> 
> LOG.error(e.message)

According to http://legacy.python.org/dev/peps/pep-0352/ the message
attribute of BaseException is deprecated since Python 2.6 and was
dropped in Python 3.0.

Christian.

-- 
Christian Berendt
Cloud Computing Solution Architect
Mail: bere...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] Logging exceptions and Python 3

[Igor Kalnitsky]

Hi,

> Is there a reason to log the exception as Unicode on Python 2?

Sure, why not? Some exceptions may have unicode message with non-ASCII
characters. and we obviously can't cast such exceptions with str() in
Python 2.x.


> The problem is that I don't know what is the best syntax to log
exceptions.

I hate this unicode dances too, since I don't understand all nuances and
potential pitfalls. But I belive the better approach is to use unicode()
for Python 2.x and str() for Python 3.x.

Example:

LOG.error(six.text_type(e))


P.S: I've a quick look over logging implementaion, and figured out
that it has some code to dial with unicode. In few words, if we know
about exception's attributes, it's better to use it directly to log:

Example:

LOG.error(e.message)


- Igor


On Thu, May 15, 2014 at 6:29 PM, Victor Stinner  wrote:

> Hi,
>
> I'm trying to define some rules to port OpenStack code to Python 3. I just
> added a section in the "Port Python 2 code to Python 3" about formatting
> exceptions and the logging module:
>
> https://wiki.openstack.org/wiki/Python3#logging_module_and_format_exceptions
>
> The problem is that I don't know what is the best syntax to log exceptions.
> Some projects convert the exception to Unicode, others use str(). I also
> saw
> six.u(str(exc)) which is wrong IMO (it can raise unicode error if the
> message
> contains a non-ASCII character).
>
> IMO the safest option is to use str(exc). For example, use
> LOG.debug(str(exc)).
>
> Is there a reason to log the exception as Unicode on Python 2?
>
> Victor
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Chris Wright]

* Stephen Wong (s3w...@midokura.com) wrote:
> Hi Chris,
> 
> Lunch time is 12:30pm (or couple minutes after that such that folks can
> grab lunch?)?

Actually shows 12:20-1:20pm on agenda.  We can start at 12:30 if you
think 10min is sufficient to grab a snack on the go.  Sorry, it's the
downside of lunch meeting w/out lunch service to pods ;/

So 12:30...

And here is the etherpad from today's starting point:

https://etherpad.openstack.org/p/juno-nfv-bof

And of course, the wiki that Russell pointed to ealier:

https://wiki.openstack.org/wiki/Meetings/NFV

thanks,
-chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] B203 table 6 for Neutron//Re: SDN NBI Core APIs consumed by OpenStack: Wednesday May 14th at 10:30-11am in the developer lounge at 3rd floor

[Tina TSOU]

Dear Salvatore,

Thank you for your comments.

Joe is the best person to explain the trust relationship and his use case.

We can describe the APIs here later.
https://wiki.openstack.org/wiki/Neutron/sdnapi


Thank you,
Tina

On May 15, 2014, at 11:45 AM, "Salvatore Orlando" 
mailto:sorla...@nicira.com>> wrote:

Hi,

frankly this picture is not worth a lot to people which did not attend this 
meetings.
At least the dumb ones like me.

I've tried to bring myself up to speed on NBI APIs; however  It is not clear 
where the mnentioned trust relationship module resides, and how it interacts 
with the other components in the picture.
Also, the role of MPLS/WAN cloud is also a bit obscure at the moment.

It would be probably not such a bad idea to create a wiki page describing 
architecture/design and action items.

However, I seem to understand that an Openstack based cloud is actually a 
energised nebula which is attracting a tie fighter whose pilot is crying for 
help shouting NBI APIs!
Sorry about the irony, I did not mean to be rude.

Regards,
Salvatore


On 15 May 2014 17:19, Tina TSOU 
mailto:tina.tsou.zout...@huawei.com>> wrote:
Dear all,

A picture is worth 1000 words.

Here is what we had in our meeting, AT&T scanario regarding trust relationship 
modle between cloud operator and network operator, and core APIs between 
OpenStack and SDN Controller for L3 VPN.




Thank you,
Tina

From: Martinx - ジェームズ 
[mailto:thiagocmarti...@gmail.com]
Sent: Wednesday, May 14, 2014 5:54 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] B203 table 6 for Neutron//Re: SDN NBI Core APIs 
consumed by OpenStack: Wednesday May 14th at 10:30-11am in the developer lounge 
at 3rd floor

Hello!

This is very an interesting topic!

I would like to talk about one idea I had, which is related to: "1.9. API for 
VPN".

I think it would be awesome, for example, when dealing with IPv6-Only "Projects 
(Tenants) Networks", the VPNs should use `Opportunistic Encryption`, this way, 
the VPNs will be established "by default" without any user interaction. Then, 
IPSec VPN for `IPv6 <-> IPv6` subnets will be always there, safely 
interconnecting the subnets, everywhere, even across different "Regions" or 
across different "Projects" (old "Tenants" terminology).

I already started a topic about this but, I'm a bit busy these days... I'll 
reply there and I'm drawing a blueprint for it...

Best!
Thiago

On 14 May 2014 12:16, Tina TSOU 
mailto:tina.tsou.zout...@huawei.com>> wrote:
Dear all,

Below is the main conclusion from this meeting.

We will work on the following SDN NBI Core APIs at the priority per Neutron's 
interest.
2, 7, 10, 9, 11.

1.2 APIs for connection between OpenStack Neutron and controller

OpenStack is widely used and deployed in cloud scenarios.OpenStack-based data 
center is becoming mainstream.

There should be APIs for connection between SDN controller and OpenStack 
Neutron.



1.7 APIs for Virtual-Tenant-Network (VTN)

VTN allows users and developers to design and deploy virtual networks without 
the need to know the physical network. This is very useful in data center.

There should be APIs for virtual tenant network.



1.10 APIs for QoS

QoS is usually for end user application. For example, the UC-SDN-Use-Case needs 
the network to guarantee its flow QoS to improve the user’s QoE.

There should be APIs for QoS.



1.9 APIs for VPN

VPN is also widely use in enterprise network, interconnectionbetween data 
centers and mobile environments.

The management and operation of VPN are necessary. There should be APIs for VPN.

The VPN may include the following type

L2 VPN

L3 VPN



1.11 APIs for network stats/state

The network stats/state is needed by application so that the application can 
react with the corresponding policy.

There should be APIs for network stats/state.


Thank you,
Tina

On May 14, 2014, at 10:00 AM, "Tina TSOU" 
mailto:tina.tsou.zout...@huawei.com>> wrote:
Dear all,

Place is changed to B203 table 6 for Networking (Neutron), Design Summit Pod 
area.


Thank you,
Tina

On May 13, 2014, at 10:00 PM, "Tina TSOU" 
mailto:tina.tsou.zout...@huawei.com>> wrote:
Dear Stackers,

We are setting up a meeting to SDN NBI Core APIs consumed by OpenStack. 
Attached is the material for your reading pleasure.

The meeting is planned for:
Wednesday May 14th at 10:30-11am in the developer lounge at 3rd 
floor .
Look forward to meeting many of you then.


Thank you,
Tina



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_

[openstack-dev] [Mistral] Cleaning up configuration settings

[W Chan]

Currently, the various configurations are registered in
./mistral/config.py.  The configurations are registered when mistral.config
is referenced.  Given the way the code is written, PEP8 throws referenced
but not used error if mistral.config is referenced but not called in the
module.  In various use cases, this is avoided by using importutils to
import mistral.config (i.e.
https://github.com/stackforge/mistral/blob/master/mistral/tests/unit/engine/test_transport.py#L34).
 I want to break down registration code in ./mistral/config.py into
separate functions for api, engine, db, etc and move the registration
closer to the module where the configuration is needed.  Any objections?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Mistral][TaskFlow] Integration plan

[Dmitri Zimine]

Renat, Joshua, Dmitri and Timur discussed the integration path for Mistral and 
TaskFlow. 
Quick summary - guys please correct any mistakes or omissions:

Taskflow - Mistral integration plan
1) Mistral: define the set of workflow primitives, define correspondent DSL
- Driven by user requirements. Keep to minimal. Implement in Mistral.
2) Taskflow: break out flow scheduler (decision maker) and persistence
- it'll be a low level "library" interference, Joshua has details
- once done, ready to re-prototype integration, iterate until happy
3) Move the primitives to TaskFlow (both teams)

4) Integrate TaskFlow into Mistral (replace Mistral workflow engine with 
TaskFlow engine)

Once integration complete, Mistral DSL will continue to work, all TaskFlow and 
Mistral workflows will be interchangeable, the code reused.

DZ. 

PS. When do we do it? We didn't commit to a date, 
but IMO (DZ) we start now, and with some luck get integrated in K cycle. 



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Stephen Wong]

Hi Steve,

Agreed. I believe Chris already suggested this meeting will reconvene
tomorrow (Friday) at lunchtime - and a number of folks already stated that
they will come.

Thanks,
- Stephen


On Thu, May 15, 2014 at 12:29 PM, Steve Gordon  wrote:

> - Original Message -
> > From: "IWAMOTO Toshihiro" 
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Sent: Wednesday, May 14, 2014 5:53:23 PM
> > Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
> >
> > At Wed, 14 May 2014 14:40:03 -0700,
> > punal patel wrote:
> > >
> > > [1  ]
> > > [1.1  ]
> > > Will this be recorded? or can I join webex?
> > >
> >
> > There's no official recording facility.  You may be able to ask
> > someone to record or stream.
> > BTW, I think it is a good idea to try to take discussion memo on
> > etherpad, just as official design summit programs.
>
> I arrived slightly late, but an etherpad was used to record some notes:
>
> https://etherpad.openstack.org/p/juno-nfv-bof
>
> Still hoping to reconvene at lunch tomorrow with the addition of those who
> couldn't make it.
>
> Steve
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Vinay Yadhav]

Hi,

Booked a slot tomorrow at 9:20 AM at the neutron pod.


Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}


On Thu, May 15, 2014 at 2:50 PM, Stephen Wong  wrote:

> Hi Vinay,
>
> I am interested. Please sign up a slot on Neutron pod for tomorrow
> (Friday) and announce the timeslot to the ML.
>
> Thanks,
> - Stephen
>
>
>
> On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav wrote:
>
>> Hi,
>>
>> I am Vinay, working with Ericsson.
>>
>> I am interested in the following blueprint regarding port mirroring
>> extension in neutron:
>> https://blueprints.launchpad.net/neutron/+spec/port-mirroring
>>
>> I am close to finishing an implementation for this extension in OVS
>> plugin and would be submitting a neutron spec related to the blueprint soon.
>>
>> I would like to know other who are also interested in introducing Port
>> Mirroring extension in neutron.
>>
>> It would be great if we can discuss and collaborate in development and
>> testing this extension
>>
>> I am currently attending the OpenStack Summit in Atlanta, so if any of
>> you are interested in the blueprint, we can meet here in the summit and
>> discuss how to proceed with the blueprint.
>>
>> Cheers,
>> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension Discussion in Neutron pod at OpenStack summit

[Vinay Yadhav]

Hi,

I have booked a slot in neutron pod at OpenStack summit tomorrow to discuss
Port Mirroring Extension in Neutron.

All interested are welcome to join in the discussion.

Time: 9:20 AM - 9:50 AM, Friday (16-05-14)

Place: Neutron POD.

Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Steve Gordon]

- Original Message -
> From: "IWAMOTO Toshihiro" 
> To: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Sent: Wednesday, May 14, 2014 5:53:23 PM
> Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
> 
> At Wed, 14 May 2014 14:40:03 -0700,
> punal patel wrote:
> > 
> > [1  ]
> > [1.1  ]
> > Will this be recorded? or can I join webex?
> > 
> 
> There's no official recording facility.  You may be able to ask
> someone to record or stream.
> BTW, I think it is a good idea to try to take discussion memo on
> etherpad, just as official design summit programs.

I arrived slightly late, but an etherpad was used to record some notes:

https://etherpad.openstack.org/p/juno-nfv-bof

Still hoping to reconvene at lunch tomorrow with the addition of those who 
couldn't make it.

Steve

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Pod-area meetup to discuss proposal to allow HV-based network selection

[Michael Dorman]

We have some folks interested in this, but want to see the Rackspace Neutron 
scaling talk (starting now.)  Will head down after it.


From: Manish Godara mailto:mani...@yahoo-inc.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, May 15, 2014 at 2:14 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Neutron] Pod-area meetup to discuss proposal to allow 
HV-based network selection

Hey folks,

I have met several folks at the summit who have come up with their own 
solutions for large clouds to allow network scaling.  Several of the solutions 
seem to be based on network selection given certain constraints.  I would like 
to discuss some use-cases and some solutions.  We could meet at 3:30/Thu 
(today) in the pod area, if interested.

Thanks,
manish
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [barbican] Barbican has completed migration to Pecan

[Chad Lung]

The Barbican team is happy to announce that we've migrated to Pecan. We
would especially like to thank Ryan Petrello for his work on switching
Barbican over to Pecan. Also, thanks to Steve Heyman for his quality
assurance work on this.

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


Thanks,

Chad Lung
http://giantflyingsaucer.com/blog/
@chadlung
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Stephen Wong]

Hi Chris,

Lunch time is 12:30pm (or couple minutes after that such that folks can
grab lunch?)?

Thanks,
- Stephen



On Thu, May 15, 2014 at 10:22 AM, Chris Wright  wrote:

> * Fawad Khaliq (fa...@plumgrid.com) wrote:
> > +1 at lunch tomorrow
> > On May 15, 2014 12:31 PM, "Hoban, Adrian" 
> wrote:
> >
> > > +1 for lunch tomorrow
>
> OK.  Let's do lunch tomorow, as Stephen suggested, in the Neutron Pod.
>
> I still plan to come today at 1:30pm, and will relay any discussion today
> to tomorrow's group for those that are leaving and can't come tomorrow.
>
> > > -Original Message-
> > > From: Chris Wright [mailto:chr...@sous-sol.org]
> > > Sent: Thursday, May 15, 2014 11:06 AM
> > > To: Steve Gordon; CARVER, PAUL; Stephen Wong; Alan Kavanagh
> > > Cc: OpenStack Development Mailing List (not for usage questions);
> > > iawe...@cisco.com
> > > Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
> > >
> > > * Stephen Wong (s3w...@midokura.com) wrote:
> > > > A good number of people involved in Neutron advanced service /
> > > > group-policy / individual services subteams will be at the Group
> > > > Policy conference session (at 1:30pm). Is it possible to reschedule
> > > > this to a different time?
> > >
> > > Urgh, we were looking at design summit sessions only.
> > >
> > > * Steve Gordon (sgor...@redhat.com) wrote:
> > > > > From: "Alan Kavanagh" 
> > > > > +1 can we reschedule to push this forward Chris please?
> > > > >
> > > > There are a number of other NFV-related sessions later in the day
> today
> > > as well (both on the general and design tracks), perhaps the best
> option
> > > would be to meet during the lunch break tomorrow instead, will enough
> > > interested people still be around?
> > >
> > > Neutron pod has 2:30 session on QoS that Sean Collins is leading.
> > > 5:00 on VLANs and gateways, (and there's a 4:10 session on SR-IOV
> that's
> > > related as well).
> > >
> > > I think it's hard to move this one.  But happy to find a time to meet
> > > again tomorrow w/ folks that couldn't make 1:30.
> > >
> > > Lunch break works for me, what about others?
> > >
> > > thanks,
> > > -chris
> > >
> > > ___
> > > OpenStack-dev mailing list
> > > OpenStack-dev@lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > > --
> > > Intel Shannon Limited
> > > Registered in Ireland
> > > Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> > > Registered Number: 308263
> > > Business address: Dromore House, East Park, Shannon, Co. Clare
> > >
> > > This e-mail and any attachments may contain confidential material for
> the
> > > sole use of the intended recipient(s). Any review or distribution by
> others
> > > is strictly prohibited. If you are not the intended recipient, please
> > > contact the sender and delete all copies.
> > >
> > >
> > >
> > > ___
> > > OpenStack-dev mailing list
> > > OpenStack-dev@lists.openstack.org
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
>
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [neutron] Meaning of qvo, qve, qbr, qr, qg and so on

[Eduard barrera]

Hi all,

I was wondering what is the meaning of this acronyms...
Are they acronyms, right ?

Quantum
Virtual
O??

Quantum
B
Ridge ?

qg ?
qve ?

What do they mean ?

Thanks
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Stephen Wong]

Hi Vinay,

I am interested. Please sign up a slot on Neutron pod for tomorrow
(Friday) and announce the timeslot to the ML.

Thanks,
- Stephen



On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav  wrote:

> Hi,
>
> I am Vinay, working with Ericsson.
>
> I am interested in the following blueprint regarding port mirroring
> extension in neutron:
> https://blueprints.launchpad.net/neutron/+spec/port-mirroring
>
> I am close to finishing an implementation for this extension in OVS plugin
> and would be submitting a neutron spec related to the blueprint soon.
>
> I would like to know other who are also interested in introducing Port
> Mirroring extension in neutron.
>
> It would be great if we can discuss and collaborate in development and
> testing this extension
>
> I am currently attending the OpenStack Summit in Atlanta, so if any of you
> are interested in the blueprint, we can meet here in the summit and discuss
> how to proceed with the blueprint.
>
> Cheers,
> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Vinay Yadhav]

Hi,

The sessions today at the pod is booked completely, we can take it
tomorrow, i will have a slot booked and mail back with the time for
tomorrow.

Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}


On Thu, May 15, 2014 at 1:36 PM, Vinay Yadhav  wrote:

> Hi,
>
> Ok then we meet up at 2:20 at the pod and see who else is interested and
> take the discussion from there.
>
> See u at the pod at 2:20 then.
>
> Cheers,
>
> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>
>
> On Thu, May 15, 2014 at 1:19 PM, Ian Wells  wrote:
>
>> There's a sheet down there.  There's actually something on at the Neutron
>> pod at that time, but you might as well meet up then and see who's
>> interested (I certainly am).
>>
>>
>> On 15 May 2014 09:31, Vinay Yadhav  wrote:
>>
>>> Hi,
>>>
>>> Cool, I propose today at 2:20 PM near the neutron pod. Can you tell me
>>> how do i sign up for it.
>>>
>>>
>>> Cheers,
>>>  main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>>>
>>>
>>> On Thu, May 15, 2014 at 12:03 PM, Kanzhe Jiang <
>>> kanzhe.ji...@bigswitch.com> wrote:
>>>
 Hi Vinay,

 I am interested. You could sign up a slot for a Network POD discussion.

 Thanks,
 Kanzhe


  On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav 
 wrote:

>  Hi,
>
> I am Vinay, working with Ericsson.
>
> I am interested in the following blueprint regarding port mirroring
> extension in neutron:
> https://blueprints.launchpad.net/neutron/+spec/port-mirroring
>
> I am close to finishing an implementation for this extension in OVS
> plugin and would be submitting a neutron spec related to the blueprint 
> soon.
>
> I would like to know other who are also interested in introducing Port
> Mirroring extension in neutron.
>
> It would be great if we can discuss and collaborate in development and
> testing this extension
>
> I am currently attending the OpenStack Summit in Atlanta, so if any of
> you are interested in the blueprint, we can meet here in the summit and
> discuss how to proceed with the blueprint.
>
> Cheers,
> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


 --
 Kanzhe Jiang
 MTS at BigSwitch

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron] Pod-area meetup to discuss proposal to allow HV-based network selection

[Manish Godara]

Hey folks,

I have met several folks at the summit who have come up with their own 
solutions for large clouds to allow network scaling.  Several of the solutions 
seem to be based on network selection given certain constraints.  I would like 
to discuss some use-cases and some solutions.  We could meet at 3:30/Thu 
(today) in the pod area, if interested.

Thanks,
manish
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][IPv6] Privacy extension

[Martinx - ジェームズ]

Hello!

I agree that there is no need for Privacy Extensions in a Cloud
environment, since MAC address are fake... No big deal...

Nevertheless, I think that should be nice to allow 1 Instance to have more
than 1 IPv6 addr, since IPv6 is (almost) virtually unlimited... This way, a
VM with, for example, a range of IPv6s to it, can have a shared host
environment when each website have its own IPv6 address (I prefer to use
IP-Based virtualhosts on Apache, instead of Name-Based)...

Cheers!
Thiago


On 15 May 2014 14:22, Ian Wells  wrote:

> I was just about to respond to that in the session when we ran out of
> time.  I would vote for simply insisting that VMs run without the privacy
> extension enabled, and only permitting the expected ipv6 address based on
> MAC.  Its primary purpose is to conceal your MAC address so that your IP
> address can't be used to track you, as I understand it, and I don't think
> that's as relevant in a cloud environment and where the MAC addresses are
> basically fake.  Someone interested in desktop virtualisation with
> Openstack may wish to contradict me...
> --
> Ian.
>
>
> On 15 May 2014 09:30, Shixiong Shang wrote:
>
>> Hi, guys:
>>
>> Nice to meet with all of you in the technical session and design session.
>> I mentioned the challenge of privacy extension in the meeting, but would
>> like to hear your opinions of how to address the problem. If you have any
>> comments or suggestions, please let me know. I will create a BP for this
>> problem.
>>
>> Thanks!
>>
>> Shixiong
>>
>>
>>  *Shixiong Shang*
>>
>>  *!--- Stay Hungry, Stay Foolish ---!*
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Core API refactoring

[Mandeep Dhami]

Thanks for the link, Fawad. I had actually seen the etherpad, but I was
hoping that there was a design document backing it up.

Regards,
Mandeep


On Thu, May 15, 2014 at 10:15 AM, Fawad Khaliq  wrote:

> Hi Mandeep,
>
> You can find discussion/details in the etherpad link[1].
>
> [1] https://etherpad.openstack.org/p/refactoring-the-neutron-core
>
> Thanks,
>
> Fawad Khaliq
> (m) +1 408.966.2214
>
>
> On Thu, May 15, 2014 at 9:40 AM, Mandeep Dhami wrote:
>
>> Hi:
>>
>> I am not at the conference this week, but it is my understanding that
>> there was a proposal for neutron core API refactoring discussed yesterday.
>> I am trying to catch up with that discussion, is there a formal design
>> description or blueprint that I can review?
>>
>> Thanks,
>> Mandeep
>> -
>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Vinay Yadhav]

Hi,

Ok then we meet up at 2:20 at the pod and see who else is interested and
take the discussion from there.

See u at the pod at 2:20 then.

Cheers,

main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}


On Thu, May 15, 2014 at 1:19 PM, Ian Wells  wrote:

> There's a sheet down there.  There's actually something on at the Neutron
> pod at that time, but you might as well meet up then and see who's
> interested (I certainly am).
>
>
> On 15 May 2014 09:31, Vinay Yadhav  wrote:
>
>> Hi,
>>
>> Cool, I propose today at 2:20 PM near the neutron pod. Can you tell me
>> how do i sign up for it.
>>
>>
>> Cheers,
>>  main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>>
>>
>> On Thu, May 15, 2014 at 12:03 PM, Kanzhe Jiang <
>> kanzhe.ji...@bigswitch.com> wrote:
>>
>>> Hi Vinay,
>>>
>>> I am interested. You could sign up a slot for a Network POD discussion.
>>>
>>> Thanks,
>>> Kanzhe
>>>
>>>
>>>  On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav wrote:
>>>
  Hi,

 I am Vinay, working with Ericsson.

 I am interested in the following blueprint regarding port mirroring
 extension in neutron:
 https://blueprints.launchpad.net/neutron/+spec/port-mirroring

 I am close to finishing an implementation for this extension in OVS
 plugin and would be submitting a neutron spec related to the blueprint 
 soon.

 I would like to know other who are also interested in introducing Port
 Mirroring extension in neutron.

 It would be great if we can discuss and collaborate in development and
 testing this extension

 I am currently attending the OpenStack Summit in Atlanta, so if any of
 you are interested in the blueprint, we can meet here in the summit and
 discuss how to proceed with the blueprint.

 Cheers,
 main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> --
>>> Kanzhe Jiang
>>> MTS at BigSwitch
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][QoS] Reminder - 2:30 PM tomorrow at the Networking pod

[Collins, Sean]

Etherpad link:

https://etherpad.openstack.org/p/qos-api-network-pod

From: , Sean Collins 
mailto:sean_colli...@cable.comcast.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, May 14, 2014 12:01 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: [openstack-dev] [Neutron][QoS] Reminder - 2:30 PM tomorrow at the 
Networking pod

Be there or be square :)
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Glance] Mid Cycle Meetup Survey

[Mark Washenberger]

Hi Folks!

Ashwhini has put together a great survey to help us plan our Glance mid
cycle meetup. Please fill it out if you think you might be interested in
attending! In particular we're trying to figure out sponsorship and
location. If you have no location preference, feel free to leave those
check boxes blank.

https://docs.google.com/forms/d/1rygMU1fXcBYn9_NgvEtjoCXlRQtlIA1UCqsQByxbTA8/viewform

Cheers,
markwash
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][IPv6] Privacy extension

[Ian Wells]

I was just about to respond to that in the session when we ran out of
time.  I would vote for simply insisting that VMs run without the privacy
extension enabled, and only permitting the expected ipv6 address based on
MAC.  Its primary purpose is to conceal your MAC address so that your IP
address can't be used to track you, as I understand it, and I don't think
that's as relevant in a cloud environment and where the MAC addresses are
basically fake.  Someone interested in desktop virtualisation with
Openstack may wish to contradict me...
-- 
Ian.


On 15 May 2014 09:30, Shixiong Shang  wrote:

> Hi, guys:
>
> Nice to meet with all of you in the technical session and design session.
> I mentioned the challenge of privacy extension in the meeting, but would
> like to hear your opinions of how to address the problem. If you have any
> comments or suggestions, please let me know. I will create a BP for this
> problem.
>
> Thanks!
>
> Shixiong
>
>
>  *Shixiong Shang*
>
>  *!--- Stay Hungry, Stay Foolish ---!*
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Chris Wright]

* Fawad Khaliq (fa...@plumgrid.com) wrote:
> +1 at lunch tomorrow
> On May 15, 2014 12:31 PM, "Hoban, Adrian"  wrote:
> 
> > +1 for lunch tomorrow

OK.  Let's do lunch tomorow, as Stephen suggested, in the Neutron Pod.

I still plan to come today at 1:30pm, and will relay any discussion today
to tomorrow's group for those that are leaving and can't come tomorrow.

> > -Original Message-
> > From: Chris Wright [mailto:chr...@sous-sol.org]
> > Sent: Thursday, May 15, 2014 11:06 AM
> > To: Steve Gordon; CARVER, PAUL; Stephen Wong; Alan Kavanagh
> > Cc: OpenStack Development Mailing List (not for usage questions);
> > iawe...@cisco.com
> > Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
> >
> > * Stephen Wong (s3w...@midokura.com) wrote:
> > > A good number of people involved in Neutron advanced service /
> > > group-policy / individual services subteams will be at the Group
> > > Policy conference session (at 1:30pm). Is it possible to reschedule
> > > this to a different time?
> >
> > Urgh, we were looking at design summit sessions only.
> >
> > * Steve Gordon (sgor...@redhat.com) wrote:
> > > > From: "Alan Kavanagh" 
> > > > +1 can we reschedule to push this forward Chris please?
> > > >
> > > There are a number of other NFV-related sessions later in the day today
> > as well (both on the general and design tracks), perhaps the best option
> > would be to meet during the lunch break tomorrow instead, will enough
> > interested people still be around?
> >
> > Neutron pod has 2:30 session on QoS that Sean Collins is leading.
> > 5:00 on VLANs and gateways, (and there's a 4:10 session on SR-IOV that's
> > related as well).
> >
> > I think it's hard to move this one.  But happy to find a time to meet
> > again tomorrow w/ folks that couldn't make 1:30.
> >
> > Lunch break works for me, what about others?
> >
> > thanks,
> > -chris
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > --
> > Intel Shannon Limited
> > Registered in Ireland
> > Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> > Registered Number: 308263
> > Business address: Dromore House, East Park, Shannon, Co. Clare
> >
> > This e-mail and any attachments may contain confidential material for the
> > sole use of the intended recipient(s). Any review or distribution by others
> > is strictly prohibited. If you are not the intended recipient, please
> > contact the sender and delete all copies.
> >
> >
> >
> > ___
> > OpenStack-dev mailing list
> > OpenStack-dev@lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >

> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Ian Wells]

There's a sheet down there.  There's actually something on at the Neutron
pod at that time, but you might as well meet up then and see who's
interested (I certainly am).


On 15 May 2014 09:31, Vinay Yadhav  wrote:

> Hi,
>
> Cool, I propose today at 2:20 PM near the neutron pod. Can you tell me how
> do i sign up for it.
>
>
> Cheers,
>  main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>
>
> On Thu, May 15, 2014 at 12:03 PM, Kanzhe Jiang  > wrote:
>
>> Hi Vinay,
>>
>> I am interested. You could sign up a slot for a Network POD discussion.
>>
>> Thanks,
>> Kanzhe
>>
>>
>>  On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav wrote:
>>
>>>  Hi,
>>>
>>> I am Vinay, working with Ericsson.
>>>
>>> I am interested in the following blueprint regarding port mirroring
>>> extension in neutron:
>>> https://blueprints.launchpad.net/neutron/+spec/port-mirroring
>>>
>>> I am close to finishing an implementation for this extension in OVS
>>> plugin and would be submitting a neutron spec related to the blueprint soon.
>>>
>>> I would like to know other who are also interested in introducing Port
>>> Mirroring extension in neutron.
>>>
>>> It would be great if we can discuss and collaborate in development and
>>> testing this extension
>>>
>>> I am currently attending the OpenStack Summit in Atlanta, so if any of
>>> you are interested in the blueprint, we can meet here in the summit and
>>> discuss how to proceed with the blueprint.
>>>
>>> Cheers,
>>> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>>>
>>> ___
>>> OpenStack-dev mailing list
>>> OpenStack-dev@lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Kanzhe Jiang
>> MTS at BigSwitch
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Core API refactoring

[Fawad Khaliq]

Hi Mandeep,

You can find discussion/details in the etherpad link[1].

[1] https://etherpad.openstack.org/p/refactoring-the-neutron-core

Thanks,

Fawad Khaliq
(m) +1 408.966.2214


On Thu, May 15, 2014 at 9:40 AM, Mandeep Dhami wrote:

> Hi:
>
> I am not at the conference this week, but it is my understanding that
> there was a proposal for neutron core API refactoring discussed yesterday.
> I am trying to catch up with that discussion, is there a formal design
> description or blueprint that I can review?
>
> Thanks,
> Mandeep
> -
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Fawad Khaliq]

+1 at lunch tomorrow
On May 15, 2014 12:31 PM, "Hoban, Adrian"  wrote:

> +1 for lunch tomorrow
>
> -Original Message-
> From: Chris Wright [mailto:chr...@sous-sol.org]
> Sent: Thursday, May 15, 2014 11:06 AM
> To: Steve Gordon; CARVER, PAUL; Stephen Wong; Alan Kavanagh
> Cc: OpenStack Development Mailing List (not for usage questions);
> iawe...@cisco.com
> Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
>
> * Stephen Wong (s3w...@midokura.com) wrote:
> > A good number of people involved in Neutron advanced service /
> > group-policy / individual services subteams will be at the Group
> > Policy conference session (at 1:30pm). Is it possible to reschedule
> > this to a different time?
>
> Urgh, we were looking at design summit sessions only.
>
> * Steve Gordon (sgor...@redhat.com) wrote:
> > > From: "Alan Kavanagh" 
> > > +1 can we reschedule to push this forward Chris please?
> > >
> > There are a number of other NFV-related sessions later in the day today
> as well (both on the general and design tracks), perhaps the best option
> would be to meet during the lunch break tomorrow instead, will enough
> interested people still be around?
>
> Neutron pod has 2:30 session on QoS that Sean Collins is leading.
> 5:00 on VLANs and gateways, (and there's a 4:10 session on SR-IOV that's
> related as well).
>
> I think it's hard to move this one.  But happy to find a time to meet
> again tomorrow w/ folks that couldn't make 1:30.
>
> Lunch break works for me, what about others?
>
> thanks,
> -chris
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> --
> Intel Shannon Limited
> Registered in Ireland
> Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
> Registered Number: 308263
> Business address: Dromore House, East Park, Shannon, Co. Clare
>
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron] Core API refactoring

[Mandeep Dhami]

Hi:

I am not at the conference this week, but it is my understanding that there
was a proposal for neutron core API refactoring discussed yesterday. I am
trying to catch up with that discussion, is there a formal design
description or blueprint that I can review?

Thanks,
Mandeep
-
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron][IPv6] Privacy extension

[Shixiong Shang]

Hi, guys:

Nice to meet with all of you in the technical session and design session. I 
mentioned the challenge of privacy extension in the meeting, but would like to 
hear your opinions of how to address the problem. If you have any comments or 
suggestions, please let me know. I will create a BP for this problem.

Thanks!

Shixiong


Shixiong Shang

!--- Stay Hungry, Stay Foolish ---!

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-docs] [Heat][Documentation] Heat template documentation

[Steve Baker]

On 15/05/14 11:54, Gauvain Pocentek wrote:
> (Resending to add openstack-dev)
>
> Gauvain Pocentek
>
> Objectif Libre - Infrastructure et Formations Linux
> http://www.objectif-libre.com
>
> Le 2014-05-15 17:34, Gauvain Pocentek a écrit :
>> Hello,
>>
>> This mail probably mainly concerns the doc team, but I guess that the
>> heat team wants to know what's going on.
>>
>> We've shortly discussed the state of heat documentation with Anne
>> Gentle and Andreas Jaeger yesterday, and I'd like to share what we
>> think would be nice to do.
>>
>> Currently we only have a small section in the user guide that
>> describes how to start a stack, but nothing documenting how to write
>> templates. The heat developer doc provides a good reference, but I
>> think it's not easy to use to get started.
>>
>> So the idea is to add an "OpenStack Orchestration" chapter in the
>> user guide that would document how to use a cloud with heat, and how
>> to write templates.
>>
>> I've drafted a spec to keep track of this at [0].
>>
>> Let me know if this sounds OK to you all.
>>
>> Gauvain Pocentek
>>
>> Objectif Libre - Infrastructure et Formations Linux
>> http://www.objectif-libre.com
>>
>> [0]:
>> https://blueprints.launchpad.net/openstack-manuals/+spec/heat-templates
>>
Thanks for raising this, I do hope I can help writing the content. In
addition to this, we will at some point need to port the resource
reference generation to this guide as well.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Vinay Yadhav]

Hi,

Cool, I propose today at 2:20 PM near the neutron pod. Can you tell me how
do i sign up for it.


Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}


On Thu, May 15, 2014 at 12:03 PM, Kanzhe Jiang
wrote:

> Hi Vinay,
>
> I am interested. You could sign up a slot for a Network POD discussion.
>
> Thanks,
> Kanzhe
>
>
> On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav wrote:
>
>> Hi,
>>
>> I am Vinay, working with Ericsson.
>>
>> I am interested in the following blueprint regarding port mirroring
>> extension in neutron:
>> https://blueprints.launchpad.net/neutron/+spec/port-mirroring
>>
>> I am close to finishing an implementation for this extension in OVS
>> plugin and would be submitting a neutron spec related to the blueprint soon.
>>
>> I would like to know other who are also interested in introducing Port
>> Mirroring extension in neutron.
>>
>> It would be great if we can discuss and collaborate in development and
>> testing this extension
>>
>> I am currently attending the OpenStack Summit in Atlanta, so if any of
>> you are interested in the blueprint, we can meet here in the summit and
>> discuss how to proceed with the blueprint.
>>
>> Cheers,
>> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Kanzhe Jiang
> MTS at BigSwitch
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Hoban, Adrian]

+1 for lunch tomorrow

-Original Message-
From: Chris Wright [mailto:chr...@sous-sol.org] 
Sent: Thursday, May 15, 2014 11:06 AM
To: Steve Gordon; CARVER, PAUL; Stephen Wong; Alan Kavanagh
Cc: OpenStack Development Mailing List (not for usage questions); 
iawe...@cisco.com
Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

* Stephen Wong (s3w...@midokura.com) wrote:
> A good number of people involved in Neutron advanced service / 
> group-policy / individual services subteams will be at the Group 
> Policy conference session (at 1:30pm). Is it possible to reschedule 
> this to a different time?

Urgh, we were looking at design summit sessions only.

* Steve Gordon (sgor...@redhat.com) wrote:
> > From: "Alan Kavanagh" 
> > +1 can we reschedule to push this forward Chris please?
> > 
> There are a number of other NFV-related sessions later in the day today as 
> well (both on the general and design tracks), perhaps the best option would 
> be to meet during the lunch break tomorrow instead, will enough interested 
> people still be around?

Neutron pod has 2:30 session on QoS that Sean Collins is leading.
5:00 on VLANs and gateways, (and there's a 4:10 session on SR-IOV that's 
related as well).

I think it's hard to move this one.  But happy to find a time to meet again 
tomorrow w/ folks that couldn't make 1:30.

Lunch break works for me, what about others?

thanks,
-chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Kanzhe Jiang]

Hi Vinay,

I am interested. You could sign up a slot for a Network POD discussion.

Thanks,
Kanzhe


On Thu, May 15, 2014 at 7:13 AM, Vinay Yadhav  wrote:

> Hi,
>
> I am Vinay, working with Ericsson.
>
> I am interested in the following blueprint regarding port mirroring
> extension in neutron:
> https://blueprints.launchpad.net/neutron/+spec/port-mirroring
>
> I am close to finishing an implementation for this extension in OVS plugin
> and would be submitting a neutron spec related to the blueprint soon.
>
> I would like to know other who are also interested in introducing Port
> Mirroring extension in neutron.
>
> It would be great if we can discuss and collaborate in development and
> testing this extension
>
> I am currently attending the OpenStack Summit in Atlanta, so if any of you
> are interested in the blueprint, we can meet here in the summit and discuss
> how to proceed with the blueprint.
>
> Cheers,
> main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Kanzhe Jiang
MTS at BigSwitch
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [keystone] [barbican] Protecting user specific secrets in Barbican

[Jarret Raim]

I just spoke with Dolph and he suggested an option that seems to solve the
problem.

In Keystone, projects that belong to domains (or other projects as the
hierarchy work moves forward) can be marked as Private, which will prevent
any role inheritance for users higher in the hierarchy.

This seems to solve the stated use case?

Arvind - does this work for you?


Thanks,
Jarret


From:  Jarret Raim 
Reply-To:  OpenStack List 
Date:  Thursday, May 15, 2014 at 11:40 AM
To:  OpenStack List 
Cc:  "Chan, Tim" , "Jones, Brant" ,
Morgan Fainberg , "Thyne, Bob" 
Subject:  Re: [openstack-dev] [keystone] [barbican] Protecting user specific
secrets in Barbican

> So let me try to summarize our conversations from yesterday.
> 
> === Use Case ===
> Assume we have a Domain D which contains a large number of individual users.
> Each user in the domain creates a public / private key. This key pair is later
> used to establish authentication to services, some not from OpenStack.
> 
> === Challenge ===
> All the user specific projects belong to the D Domain. This means that any
> user with read permissions on the domain will be able to access the user
> specific secrets. As it seems likely that many users will be given domain read
> permissions, this violates least privilege by allowing a large number of users
> access to secret data that they don't need.
> 
> === Initial Proposal ===
> The original proposal was to scope secrets to a composite key of the project
> id and the user id from the user who created the secret. There is some concern
> from both Keystone and Barbican members that this approach violates the base
> assumption that, in OpenStack, the lowest level of authorization is a project.
> 
> === Open Question ===
> My current thinking is that since these keys are user specific and Keystone
> owns the user resource in OpenStack, it is starting to feel like this type of
> data should more properly be owned by the Keystone service rather than
> Barbican. Of course, Keystone could use Barbican for backend storage if
> desired.
> 
> 
> I'd really like to get some feedback from the Keystone folks on how they think
> about this one as, more and more, it's feeling like a problem that Barbican
> shouldn't solve. 
> 
> 
> Thanks,
> Jarret
> 
> 
> From: , Arvind 
> Reply-To: OpenStack List 
> Date: Thursday, May 15, 2014 at 8:21 AM
> To: OpenStack List 
> Cc: "Jones, Brant" , "Chan, Tim" ,
> "Thyne, Bob" , Morgan Fainberg 
> Subject: [openstack-dev] [keystone] [barbican] Protecting user specific
> secrets in Barbican
> 
>> Barbcan will be used as secret store (or Key Manager) in Open Stack
>> deployments. That means users can store any kind for secrets (ssh keys ,
>> access keys, password Š..) in Barbican these secrets are not shared secrets.
>>  
>> In below scenario it seems secrets are not well protected in Barbican
>>  
>> 1.  Barbican in integrated a OS based cloud deployment.
>> 
>> 2.  In particular domain there is one (or multiple) project.
>> 
>> 3.  Users are associated with the project through role (two coworker can
>> have same role e.g. creator) or a admin user have higher role.
>> 
>> 4.  Users have their secrets (ssh keys , access keys, password Š..) for
>> services (VMs per users, resources) saved in Barbican.
>> 
>>  
>>  
>> Problem
>>  
>> 1.  Users with the same role or Admin on project can see each other
>> secrets which are not a shared secrets.
>> 
>> 2.  Multiple projects (or project hierarchy) per user just to store
>> secrets is not going to help as it will lead to project exposition and
>> confusing. At the same time projects are not meant to go 1 to 1 with user.
>> 
>> 3.  Project hierarchy is also not a good solution as user on top of the
>> hierarchy (reseller admin) can inherits role and able to steal the secrets.
>> 
>>  
>>  
>> Note, Barbican is designed for secret storage and protection, we need better
>> management on secrets in Barbican. We also need better solution to address
>> this problem.
>>  
>>  
>> Keystone and Barbican (or interested party) team, can we have a meeting today
>> to brainstorm this issue and come up with better solution?
>>  
>>  
>> Thanks
>> Arvind  
>>  
>>  
>>  




smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-docs] [Heat][Documentation] Heat template documentation

[Gauvain Pocentek]

(Resending to add openstack-dev)

Gauvain Pocentek

Objectif Libre - Infrastructure et Formations Linux
http://www.objectif-libre.com

Le 2014-05-15 17:34, Gauvain Pocentek a écrit :

Hello,

This mail probably mainly concerns the doc team, but I guess that the
heat team wants to know what's going on.

We've shortly discussed the state of heat documentation with Anne
Gentle and Andreas Jaeger yesterday, and I'd like to share what we
think would be nice to do.

Currently we only have a small section in the user guide that
describes how to start a stack, but nothing documenting how to write
templates. The heat developer doc provides a good reference, but I
think it's not easy to use to get started.

So the idea is to add an "OpenStack Orchestration" chapter in the
user guide that would document how to use a cloud with heat, and how
to write templates.

I've drafted a spec to keep track of this at [0].

Let me know if this sounds OK to you all.

Gauvain Pocentek

Objectif Libre - Infrastructure et Formations Linux
http://www.objectif-libre.com

[0]: 
https://blueprints.launchpad.net/openstack-manuals/+spec/heat-templates


___
Openstack-docs mailing list
openstack-d...@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [sahara] Nominate Trevor McKay for sahara-core

[John Speidel]

+1
Excellent addition.

-John


On Tue, May 13, 2014 at 2:26 PM, Andrew Lazarev wrote:

> +1
>
> It will be good addition to the core team.
>
> Thanks,
> Andrew.
>
>
>
>
> On Mon, May 12, 2014 at 2:31 PM, Sergey Lukjanov 
> wrote:
>
>> Hey folks,
>>
>> I'd like to nominate Trevor McKay (tmckay) for sahara-core.
>>
>> He is among the top reviewers of Sahara subprojects. Trevor is working
>> on Sahara full time since summer 2013 and is very familiar with
>> current codebase. His code contributions and reviews have demonstrated
>> a good knowledge of Sahara internals. Trevor has a valuable knowledge
>> of EDP part and Hadoop itself. He's working on both bugs and new
>> features implementation.
>>
>> Some links:
>>
>> http://stackalytics.com/report/contribution/sahara-group/30
>> http://stackalytics.com/report/contribution/sahara-group/90
>> http://stackalytics.com/report/contribution/sahara-group/180
>>
>> https://review.openstack.org/#/q/owner:tmckay+sahara+AND+-status:abandoned,n,z
>> https://launchpad.net/~tmckay
>>
>> Sahara cores, please, reply with +1/0/-1 votes.
>>
>> Thanks.
>>
>> --
>> Sincerely yours,
>> Sergey Lukjanov
>> Sahara Technical Lead
>> (OpenStack Data Processing)
>> Mirantis Inc.
>>
>> ___
>> OpenStack-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [keystone] [barbican] Protecting user specific secrets in Barbican

[Jarret Raim]

So let me try to summarize our conversations from yesterday.

=== Use Case ===
Assume we have a Domain D which contains a large number of individual users.
Each user in the domain creates a public / private key. This key pair is
later used to establish authentication to services, some not from OpenStack.

=== Challenge ===
All the user specific projects belong to the D Domain. This means that any
user with read permissions on the domain will be able to access the user
specific secrets. As it seems likely that many users will be given domain
read permissions, this violates least privilege by allowing a large number
of users access to secret data that they don't need.

=== Initial Proposal ===
The original proposal was to scope secrets to a composite key of the project
id and the user id from the user who created the secret. There is some
concern from both Keystone and Barbican members that this approach violates
the base assumption that, in OpenStack, the lowest level of authorization is
a project.

=== Open Question ===
My current thinking is that since these keys are user specific and Keystone
owns the user resource in OpenStack, it is starting to feel like this type
of data should more properly be owned by the Keystone service rather than
Barbican. Of course, Keystone could use Barbican for backend storage if
desired.


I'd really like to get some feedback from the Keystone folks on how they
think about this one as, more and more, it's feeling like a problem that
Barbican shouldn't solve.


Thanks,
Jarret


From:  , Arvind 
Reply-To:  OpenStack List 
Date:  Thursday, May 15, 2014 at 8:21 AM
To:  OpenStack List 
Cc:  "Jones, Brant" , "Chan, Tim" ,
"Thyne, Bob" , Morgan Fainberg 
Subject:  [openstack-dev] [keystone] [barbican] Protecting user specific
secrets in Barbican

> Barbcan will be used as secret store (or Key Manager) in Open Stack
> deployments. That means users can store any kind for secrets (ssh keys ,
> access keys, password Š..) in Barbican these secrets are not shared secrets.
>  
> In below scenario it seems secrets are not well protected in Barbican
>  
> 1.  Barbican in integrated a OS based cloud deployment.
> 
> 2.  In particular domain there is one (or multiple) project.
> 
> 3.  Users are associated with the project through role (two coworker can
> have same role e.g. creator) or a admin user have higher role.
> 
> 4.  Users have their secrets (ssh keys , access keys, password Š..) for
> services (VMs per users, resources) saved in Barbican.
> 
>  
>  
> Problem
>  
> 1.  Users with the same role or Admin on project can see each other
> secrets which are not a shared secrets.
> 
> 2.  Multiple projects (or project hierarchy) per user just to store
> secrets is not going to help as it will lead to project exposition and
> confusing. At the same time projects are not meant to go 1 to 1 with user.
> 
> 3.  Project hierarchy is also not a good solution as user on top of the
> hierarchy (reseller admin) can inherits role and able to steal the secrets.
> 
>  
>  
> Note, Barbican is designed for secret storage and protection, we need better
> management on secrets in Barbican. We also need better solution to address
> this problem.
>  
>  
> Keystone and Barbican (or interested party) team, can we have a meeting today
> to brainstorm this issue and come up with better solution?
>  
>  
> Thanks
> Arvind  
>  
>  
>  




smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [sahara] Nominate Trevor McKay for sahara-core

[Matthew Farrellee]

On 05/12/2014 05:31 PM, Sergey Lukjanov wrote:

Hey folks,

I'd like to nominate Trevor McKay (tmckay) for sahara-core.

He is among the top reviewers of Sahara subprojects. Trevor is working
on Sahara full time since summer 2013 and is very familiar with
current codebase. His code contributions and reviews have demonstrated
a good knowledge of Sahara internals. Trevor has a valuable knowledge
of EDP part and Hadoop itself. He's working on both bugs and new
features implementation.

Some links:

http://stackalytics.com/report/contribution/sahara-group/30
http://stackalytics.com/report/contribution/sahara-group/90
http://stackalytics.com/report/contribution/sahara-group/180
https://review.openstack.org/#/q/owner:tmckay+sahara+AND+-status:abandoned,n,z
https://launchpad.net/~tmckay

Sahara cores, please, reply with +1/0/-1 votes.

Thanks.



+1

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [oslo] strutils: enhance safe_decode() and safe_encode()

[Victor Stinner]

Hi,

The functions safe_decode() and safe_encode() have been ported to Python 3, 
and changed more than once. IMO we can still improve these functions to make 
them more reliable and easier to use.


(1) My first concern is that these functions try to guess user expectation 
about encodings. They use "sys.stdin.encoding or sys.getdefaultencoding()" as 
the default encoding to decode, but this encoding depends on the locale 
encoding (stdin encoding), on stdin (is stdin a TTY? is stdin mocked?), and on 
the Python major version.

IMO the default encoding should be UTF-8 because most OpenStack components 
expect this encoding.

Or maybe users want to display data to the terminal, and so the locale 
encoding should be used? In this case, locale.getpreferredencoding() would be 
more reliable than sys.stdin.encoding.


(2) My second concern is that safe_encode(bytes, incoming, encoding) 
transcodes the bytes string from incoming to encoding if these two encodings 
are different.

When I port code to Python 3, I'm looking for a function to replace this 
common pattern:

if isinstance(data, six.text_type):
data = data.encode(encoding)

I don't want to modify data encoding if it is already a bytes string. So I 
would prefer to have:

def safe_encode(data, encoding='utf-8'):
if isinstance(data, six.text_type):
data = data.encode(encoding)
return data

Changing safe_encode() like this will break applications relying on the 
"transcode" feature (incoming => encoding). If such usage exists, I suggest to 
add a new function (ex: "transcode" ?) with an API fitting this use case. For 
example, the incoming encoding would be mandatory.

Is there really applications using the incoming parameter?


So, what do you think about that?

Victor

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [oslo] Logging exceptions and Python 3

[Victor Stinner]

Hi,

I'm trying to define some rules to port OpenStack code to Python 3. I just 
added a section in the "Port Python 2 code to Python 3" about formatting 
exceptions and the logging module:
https://wiki.openstack.org/wiki/Python3#logging_module_and_format_exceptions

The problem is that I don't know what is the best syntax to log exceptions. 
Some projects convert the exception to Unicode, others use str(). I also saw 
six.u(str(exc)) which is wrong IMO (it can raise unicode error if the message 
contains a non-ASCII character).

IMO the safest option is to use str(exc). For example, use 
LOG.debug(str(exc)).

Is there a reason to log the exception as Unicode on Python 2?

Victor

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Chris Wright]

* Stephen Wong (s3w...@midokura.com) wrote:
> A good number of people involved in Neutron advanced service /
> group-policy / individual services subteams will be at the Group
> Policy
> conference session (at 1:30pm). Is it possible to reschedule this to a
> different time?

Urgh, we were looking at design summit sessions only.

* Steve Gordon (sgor...@redhat.com) wrote:
> > From: "Alan Kavanagh" 
> > +1 can we reschedule to push this forward Chris please?
> > 
> There are a number of other NFV-related sessions later in the day today as 
> well (both on the general and design tracks), perhaps the best option would 
> be to meet during the lunch break tomorrow instead, will enough interested 
> people still be around?

Neutron pod has 2:30 session on QoS that Sean Collins is leading.
5:00 on VLANs and gateways, (and there's a 4:10 session on SR-IOV that's
related as well).

I think it's hard to move this one.  But happy to find a time to meet again
tomorrow w/ folks that couldn't make 1:30.

Lunch break works for me, what about others?

thanks,
-chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Stephen Wong]

+1 for lunch break tomorrow (Friday) - we can still meet at the Neutron pod


On Thu, May 15, 2014 at 7:27 AM, Steve Gordon  wrote:

> - Original Message -
> > From: "Alan Kavanagh" 
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> > Cc: iawe...@cisco.com
> > Sent: Thursday, May 15, 2014 10:02:49 AM
> > Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
> >
> > +1 can we reschedule to push this forward Chris please?
> >
> > Alan
>
> There are a number of other NFV-related sessions later in the day today as
> well (both on the general and design tracks), perhaps the best option would
> be to meet during the lunch break tomorrow instead, will enough interested
> people still be around?
>
> Thanks,
>
> Steve
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Eugene Nikanorov]

Vijay,

Pools-monitors are still many to many, if it's not so on the picture -
we'll fix that.
I brought this up as an example of how we dealt with m:n via API.

Thanks,
Eugene.


On Thu, May 15, 2014 at 6:43 PM, Vijay Venkatachalam <
vijay.venkatacha...@citrix.com> wrote:

>  Thanks for the clarification. Eugene.
>
>
>
> A tangential point since you brought healthmon and pool.
>
>
>
> There will be an additional entity called ‘PoolMonitorAssociation’ which
> results in a many to many relationship between pool and monitors. Right?
>
>
>
> Now, the model is indicating a pool can have only one monitor. So a minor
> correction is required to indicate the many to many relationship via
> PoolMonitorAssociation.
>
>
>
> Thanks,
>
> Vijay V.
>
>
>
>
>
> *From:* Eugene Nikanorov [mailto:enikano...@mirantis.com]
> *Sent:* Thursday, May 15, 2014 7:36 PM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?
>
>
>
> Hi Vijay,
>
>
>
>
> When you say API is not available, it means this should not be considered
> like a resource/entity. Correct?
>
>
>
> But then, there would be API like a bind API, that accepts loadbalancer_id
> & listener_id,  which creates this object.
>
> And also, there would be an API that will be used to list the listeners of
> a LoadBalancer.
>
>
>
> Right?
>
>  Right, that's the same as health monitors and pools work right now:
> there are separate REST action to associate healthmon to a pool
>
>
>
>
>
> Thanks,
>
> Eugene.
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Eugene Nikanorov]

Hi Iwamoto,

I think you may want to talk to Mark MacClain on why we want to move to
flavors instead of letting user to chose implementation.
Basically the arguments against flavors (flexible mapping) are based on
some lack of understanding of cloud operator requirements.
Ability to chose provider was the first simplistic step in allowing
multivendor support, but it appeared to be not much convenient for cloud
operators.

And obviously implementation details (especially vendor-specific) should be
hidden behind API, that's the goal of all OS services to abstract tenant
from that.

Thanks,
Eugene.


On Thu, May 15, 2014 at 6:45 PM, IWAMOTO Toshihiro wrote:

> It is pity to see enoumous LBaaS efforts have been largely spinning
> (in a sense of spinlocks) for a while.
>
> At Thu, 15 May 2014 14:31:54 +0400,
> Eugene Nikanorov wrote:
> >
> > [1  ]
> > [1.1  ]
> > Hi Craig,
> >
> > Implementation-specific options are not exposed through the API, or
> > otherwise it would be inconsistent, given that we are moving to a
> > flavor-based approach of specifying service requirements where
> > implementation is completely hidden from the user.
>
> There was a lot of arguments against your flavor proposal at the
> design summit session and at the meeting at the pod area.
> So, it is not clear if "moving to a flavor-based" happens in a
> reasonalbe timeframe.
>
> OTOH, the flavor framework is not much more than a bitmap matching of
> feature vectors.  I think something is not going right as we spent
> good 30mins on this topic at the pod area.
>
> We'll be able to continue the same technical level argument at home as
> we did for the last couple of months.
>
> My suggestion is to try to discuss differently here at the summit.
>
> --
> IWAMOTO Toshihiro
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Vijay Venkatachalam]

Thanks for the clarification. Eugene.

A tangential point since you brought healthmon and pool.

There will be an additional entity called ‘PoolMonitorAssociation’ which 
results in a many to many relationship between pool and monitors. Right?

Now, the model is indicating a pool can have only one monitor. So a minor 
correction is required to indicate the many to many relationship via 
PoolMonitorAssociation.

Thanks,
Vijay V.


From: Eugene Nikanorov [mailto:enikano...@mirantis.com]
Sent: Thursday, May 15, 2014 7:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Hi Vijay,


When you say API is not available, it means this should not be considered like 
a resource/entity. Correct?

But then, there would be API like a bind API, that accepts loadbalancer_id & 
listener_id,  which creates this object.
And also, there would be an API that will be used to list the listeners of a 
LoadBalancer.

Right?
Right, that's the same as health monitors and pools work right now: there are 
separate REST action to associate healthmon to a pool


Thanks,
Eugene.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[IWAMOTO Toshihiro]

It is pity to see enoumous LBaaS efforts have been largely spinning
(in a sense of spinlocks) for a while.

At Thu, 15 May 2014 14:31:54 +0400,
Eugene Nikanorov wrote:
> 
> [1  ]
> [1.1  ]
> Hi Craig,
> 
> Implementation-specific options are not exposed through the API, or
> otherwise it would be inconsistent, given that we are moving to a
> flavor-based approach of specifying service requirements where
> implementation is completely hidden from the user.

There was a lot of arguments against your flavor proposal at the
design summit session and at the meeting at the pod area.
So, it is not clear if "moving to a flavor-based" happens in a
reasonalbe timeframe.

OTOH, the flavor framework is not much more than a bitmap matching of
feature vectors.  I think something is not going right as we spent
good 30mins on this topic at the pod area.

We'll be able to continue the same technical level argument at home as
we did for the last couple of months.

My suggestion is to try to discuss differently here at the summit.

--
IWAMOTO Toshihiro

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [NFV] New Sub-team and Meeting

[Chris Wright]

* Russell Bryant (rbry...@redhat.com) wrote:
> It is clear that a number of us have been working independently on NFV
> related features.  It would be beneficial to start doing some
> coordination in this area.  To do that, I think we should form an NFV
> group with a regular IRC meeting.  I'd like to see this group be a
> collaboration of developers, deployers, and end users working together
> to make sure we are successful in supporting NFV use cases.

Great idea to bring folks together to form some concerted effort.

> Proposed set of goals for this group:
> 
>  * Organize documentation on the OpenStack wiki of use cases and gaps to
> be filled in OpenStack.

Some of this information is slowly being built (in a more generic
fashion) with the ETSI NFV group.  So getting this translated more
directly into OpenStack language is probably a good start.

thanks,
-chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Steve Gordon]

- Original Message -
> From: "Alan Kavanagh" 
> To: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Cc: iawe...@cisco.com
> Sent: Thursday, May 15, 2014 10:02:49 AM
> Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit
> 
> +1 can we reschedule to push this forward Chris please?
> 
> Alan

There are a number of other NFV-related sessions later in the day today as well 
(both on the general and design tracks), perhaps the best option would be to 
meet during the lunch break tomorrow instead, will enough interested people 
still be around?

Thanks,

Steve

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[CARVER, PAUL]

Port mirroring is definitely a topic that I hear coming from network 
operations. The netops folks are accustomed to having sniffers all over the 
place and being able to span switch ports as a first step in network 
troubleshooting. The concern about "how do I span a port" is one of the first 
questions a netops person wants answered when we talk about cloud.



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Murano] Meet Murano developers at Atlanta summit

[Ruslan Kamaldinov]

On Wed, May 14, 2014 at 1:31 PM, Ruslan Kamaldinov
 wrote:
> We've seen a lot of interest in Murano at the Atlanta summit. In case
> if you would like to learn more, please stop by Mirantis booth (1st
> level) tomorrow (Thursday) from from 3PM to 5PM. Murano developers
> will be there and they will be happy to show you the demo in give more
> details.
>
> --
> Ruslan


Uh oh. Markeеplace on level 1 is closed today. We will be at the
developer lounge in the B301-B306 area. Time is the same - from 3PM to
5PM on Thursday.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Meet up time at the summit for a POD; Re: Pluggable IPAM

[Justin Hammond]

There were some concerns about the ML2 design meeting and this one. Unless 
there are objections we intend on keeping the IPAM POD at 11:30.

My availability is wide open except for 2:30-4:10 (due to my talk).

Please respond if you have concerns, otherwise those who have stated their 
interest are still meeting at 11:30.

From: Justin Hammond 
mailto:justin.hamm...@rackspace.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thu, 15 May 2014 03:16:13 +
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Meet up time at the summit for a POD; 
Re: Pluggable IPAM

Yes sorry. May 15. The neutron pod is on level 2. You can get to it from level 
3 if you go into the developer lounge, go down the spiral staircase surrounded 
by the curtains, then hang a slight right. I believe it is room 204? It says 
'neutron' on the list of PODs.

From: Maksym Lobur mailto:mlo...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Thu, 15 May 2014 06:02:15 +0300
To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Meet up time at the summit for a POD; 
Re: Pluggable IPAM

I'm sorry, you meant May 15, right?
What is the neutron POD?

Best regards,
Max Lobur,
Python Developer, Mirantis, Inc.

Mobile: +38 (093) 665 14 28
Skype: max_lobur

38, Lenina ave. Kharkov, Ukraine
www.mirantis.com
www.mirantis.ru


On Wed, May 14, 2014 at 8:06 PM, Justin Hammond 
mailto:justin.hamm...@rackspace.com>> wrote:
Signed up for 11:30 AM, May 14 at the neutron POD.

On 5/14/14 12:29 PM, "Justin Hammond" 
mailto:justin.hamm...@rackspace.com>> wrote:

>John Voss and I believe Thursday (May 15) would be the best time to do
>this. I will write it on the board.
>
>On 5/14/14 11:59 AM, "Justin Hammond" 
>mailto:justin.hamm...@rackspace.com>>
>wrote:
>
>>I also intend on advertising this during the core-refactoring session in
>>the etherpad. Please pay attention to that if you're there!
>>
>>
>>
>>___
>>OpenStack-dev mailing list
>>OpenStack-dev@lists.openstack.org
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>___
>OpenStack-dev mailing list
>OpenStack-dev@lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___ OpenStack-dev mailing list 
OpenStack-dev@lists.openstack.org 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___ OpenStack-dev mailing list 
OpenStack-dev@lists.openstack.org 
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Openstack-dev][Neutron] Port Mirroring Extension in Neutron

[Vinay Yadhav]

Hi,

I am Vinay, working with Ericsson.

I am interested in the following blueprint regarding port mirroring
extension in neutron:
https://blueprints.launchpad.net/neutron/+spec/port-mirroring

I am close to finishing an implementation for this extension in OVS plugin
and would be submitting a neutron spec related to the blueprint soon.

I would like to know other who are also interested in introducing Port
Mirroring extension in neutron.

It would be great if we can discuss and collaborate in development and
testing this extension

I am currently attending the OpenStack Summit in Atlanta, so if any of you
are interested in the blueprint, we can meet here in the summit and discuss
how to proceed with the blueprint.

Cheers,
main(i){putchar((5852758>>((i-1)/2)*8)-!(1&i)*'\r')^89&&main(++i);}
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Eugene Nikanorov]

Hi Vijay,

>
>
>
> When you say API is not available, it means this should not be considered
> like a resource/entity. Correct?
>
>
>
> But then, there would be API like a bind API, that accepts loadbalancer_id
> & listener_id,  which creates this object.
>
> And also, there would be an API that will be used to list the listeners of
> a LoadBalancer.
>
>
>
> Right?
>
Right, that's the same as health monitors and pools work right now: there
are separate REST action to associate healthmon to a pool


Thanks,
Eugene.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [NFV] New Sub-team and Meeting

[Russell Bryant]

On 05/15/2014 09:58 AM, Stephen Wong wrote:
> Hi Russ,
> 
> Are you in Atlanta? If so, should we find a time to meet at (for
> example) the Neutron pod area for face to face meeting over the next two
> days?

There's a BoF today at 1:30 pm.

http://lists.openstack.org/pipermail/openstack-dev/2014-May/035027.html

I'm planning to be there and will discuss this.

-- 
Russell Bryant

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [NFV] New Sub-team and Meeting

[Russell Bryant]

On 05/15/2014 09:51 AM, balaj...@freescale.com wrote:
> Hi Russell,
> 
> Are we going to bring all the NFV efforts happening in multiple projects like 
> FWaaS, Service VM etc under one roof.
> 
> Just curious to know the objective of this NFV sub-team.

I think if a given effort has enough people and momentum that they have
already organized with a meeting and such, I certainly don't want to
stop that.  However, I think it would be nice to have a representative
from each of these things to stop by and report status and raise
awareness of any areas where additional help is needed.  We're going to
be tracking requirements around NFV and matching up development efforts
to those, so we'll certainly be interested in those things.

If there's not already a team/meeting around a particular effort, we can
certainly drive it through this group.

-- 
Russell Bryant

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [NFV] New Sub-team and Meeting

[Stephen Wong]

Hi Russ,

Are you in Atlanta? If so, should we find a time to meet at (for
example) the Neutron pod area for face to face meeting over the next two
days?

Thanks,
- Stephen



On Thu, May 15, 2014 at 6:43 AM, Russell Bryant  wrote:

> It is clear that a number of us have been working independently on NFV
> related features.  It would be beneficial to start doing some
> coordination in this area.  To do that, I think we should form an NFV
> group with a regular IRC meeting.  I'd like to see this group be a
> collaboration of developers, deployers, and end users working together
> to make sure we are successful in supporting NFV use cases.
>
> Proposed set of goals for this group:
>
>  * Organize documentation on the OpenStack wiki of use cases and gaps to
> be filled in OpenStack.
>
>  * Identify relevant development efforts across OpenStack (designs,
> code) and track their progress.
>
>- Provide a page for interested parties to quickly see the status
>  across these efforts
>
>- Highlight areas that need additional help.
>
>  * Provide a meeting where people can get together and discuss this work
>on a regular basis.
>
> To get us started, I have created the following wiki page with some
> information on some of the efforts already under way.  I welcome help
> filling it in with more details.
>
> https://wiki.openstack.org/wiki/Meetings/NFV
>
> For the IRC meeting, I propose we start meeting in a couple weeks with
> the first one on Wednesday, June 4 at 1400 UTC in #openstack-meeting.
> It's going to be tough to pick a date/time that works for everyone, but
> if this absolutely does not work for you and you'd like to participate,
> feedback is welcome.
>
> For discussions outside of the meeting about these features, I think we
> should use the openstack-dev mailing list.  When posting about NFV,
> please use the [NFV] tag in the message subject.
>
> Thanks!
>
> --
> Russell Bryant
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Alan Kavanagh]

+1 can we reschedule to push this forward Chris please?

Alan

From: Stephen Wong [mailto:s3w...@midokura.com]
Sent: May-15-14 10:01 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: iawe...@cisco.com
Subject: Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

Hi Chris,

A good number of people involved in Neutron advanced service / group-policy 
/ individual services subteams will be at the Group Policy conference session 
(at 1:30pm). Is it possible to reschedule this to a different time?

Thanks,
- Stephen

On Wed, May 14, 2014 at 10:06 AM, Chris Wright 
mailto:chr...@redhat.com>> wrote:
Thursday at 1:30 PM in the Neutron Pod we'll do
an NFV BoF.  If you are at design summit and
interested in Neutron + NFV please come join us.

thanks,
-chris

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Vijay Venkatachalam]

Hi Stephen:


* The LBtoListener object is grayed out because it will need to exist in the 
database (to allow Listeners to be re-used, solving the IPv4 + IPv6 common use 
case), but should not be directly addressable via the user API. (This is also 
the reason it's got no tenant_id.)

When you say API is not available, it means this should not be considered like 
a resource/entity. Correct?

But then, there would be API like a bind API, that accepts loadbalancer_id & 
listener_id,  which creates this object.
And also, there would be an API that will be used to list the listeners of a 
LoadBalancer.

Right?

* The vip group and vip anti group stuff is meant to solve the vip colocation / 
apolocation problem. These are optional objects that don't need to be created 
unless a user has colocation / apolocation needs.  (I'd be happy to run anyone 
through the logic on how these work, as it's probably not immediately 
intuitive.)
Yes please, could you explain on the ML!

Thanks,
Vijay V.


From: Stephen Balukoff [mailto:sbaluk...@bluebox.net]
Sent: Wednesday, May 14, 2014 11:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

Aah--  and here's a small error correction. :)

Please also note:
* We're not yet in consensus on the L7 or SSL related objects, but the 
Loadbalancer, Listener, Pool, and Member should probably not change at this 
point (unless there are major objections voiced in the very near term).
* I've tried to use color coordination to indicate different logical parts that 
can probably be implemented in different blueprints / by different engineering 
teams.
* The LBtoListener object is grayed out because it will need to exist in the 
database (to allow Listeners to be re-used, solving the IPv4 + IPv6 common use 
case), but should not be directly addressable via the user API. (This is also 
the reason it's got no tenant_id.)
* The vip group and vip anti group stuff is meant to solve the vip colocation / 
apolocation problem. These are optional objects that don't need to be created 
unless a user has colocation / apolocation needs.  (I'd be happy to run anyone 
through the logic on how these work, as it's probably not immediately 
intuitive.)

Stephen


On Wed, May 14, 2014 at 10:22 AM, Stephen Balukoff 
mailto:sbaluk...@bluebox.net>> wrote:
Also, apologies for the crappy formatting. I like gv files as they're easily 
tracked in a text-based revision control system (like git) that depends on 
useful diffs to do code reviews. But sometimes the layout it chooses is a 
little dumb.

Stephen

On Wed, May 14, 2014 at 10:18 AM, Stephen Balukoff 
mailto:sbaluk...@bluebox.net>> wrote:
Hi Craig,

I'm attaching the latest object model diagram as discussed with the RAX team 
last night, Samuel and Eugene. Note that we don't necessarily have HP's 
blessing on this model yet, nor do we have Neutron core developer buy in.  But 
in any case, here it is.

Also, I think the #openstack-lbaas channel is a great idea!

Stephen

On Wed, May 14, 2014 at 9:05 AM, Craig Tracey 
mailto:cr...@craigtracey.com>> wrote:
Hi all,

From what I heard last night, it sounds like there has been some consensus 
achieved around the LBaaS object model.  Unfortunately, I missed this ad-hoc 
conversation.  Is someone capturing this information and/or perhaps posting to 
the list? someplace else?

On a related note, does it make sense to create an lbaas IRC topic channel?  
#openstack-lbaas?  Just thinking that a dedicated channel might help to make 
the weekly meetings more productive with less crosstalk.  Thoughts?

Best,
Craig

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807



--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807



--
Stephen Balukoff
Blue Box Group, LLC
(800)613-4305 x807
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Stephen Wong]

Hi Chris,

A good number of people involved in Neutron advanced service /
group-policy / individual services subteams will be at the Group Policy
conference session (at 1:30pm). Is it possible to reschedule this to a
different time?

Thanks,
- Stephen


On Wed, May 14, 2014 at 10:06 AM, Chris Wright  wrote:

> Thursday at 1:30 PM in the Neutron Pod we'll do
> an NFV BoF.  If you are at design summit and
> interested in Neutron + NFV please come join us.
>
> thanks,
> -chris
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [NFV] New Sub-team and Meeting

[balaj...@freescale.com]

Hi Russell,

Are we going to bring all the NFV efforts happening in multiple projects like 
FWaaS, Service VM etc under one roof.

Just curious to know the objective of this NFV sub-team.

Regards,
Balaji.P

> -Original Message-
> From: Russell Bryant [mailto:rbry...@redhat.com]
> Sent: Thursday, May 15, 2014 7:13 PM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [NFV] New Sub-team and Meeting
> 
> It is clear that a number of us have been working independently on NFV
> related features.  It would be beneficial to start doing some
> coordination in this area.  To do that, I think we should form an NFV
> group with a regular IRC meeting.  I'd like to see this group be a
> collaboration of developers, deployers, and end users working together to
> make sure we are successful in supporting NFV use cases.
> 
> Proposed set of goals for this group:
> 
>  * Organize documentation on the OpenStack wiki of use cases and gaps to
> be filled in OpenStack.
> 
>  * Identify relevant development efforts across OpenStack (designs,
> code) and track their progress.
> 
>- Provide a page for interested parties to quickly see the status
>  across these efforts
> 
>- Highlight areas that need additional help.
> 
>  * Provide a meeting where people can get together and discuss this work
>on a regular basis.
> 
> To get us started, I have created the following wiki page with some
> information on some of the efforts already under way.  I welcome help
> filling it in with more details.
> 
> https://wiki.openstack.org/wiki/Meetings/NFV
> 
> For the IRC meeting, I propose we start meeting in a couple weeks with
> the first one on Wednesday, June 4 at 1400 UTC in #openstack-meeting.
> It's going to be tough to pick a date/time that works for everyone, but
> if this absolutely does not work for you and you'd like to participate,
> feedback is welcome.
> 
> For discussions outside of the meeting about these features, I think we
> should use the openstack-dev mailing list.  When posting about NFV,
> please use the [NFV] tag in the message subject.
> 
> Thanks!
> 
> --
> Russell Bryant
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][NFV] NFV BoF at design summit

[Russell Bryant]

On 05/14/2014 05:53 PM, IWAMOTO Toshihiro wrote:
> At Wed, 14 May 2014 14:40:03 -0700,
> punal patel wrote:
>>
>> [1  ]
>> [1.1  ]
>> Will this be recorded? or can I join webex?
>>
> 
> There's no official recording facility.  You may be able to ask
> someone to record or stream.
> BTW, I think it is a good idea to try to take discussion memo on
> etherpad, just as official design summit programs.

I would also like to see some regular discussion and coordination after
the summit on these things.  See this message for more:

http://lists.openstack.org/pipermail/openstack-dev/2014-May/035068.html

-- 
Russell Bryant

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS]LBaaS 1st Session etherpad

[Vijay Venkatachalam]

Ok, thanks.

So Listeners are indeed created independent of Loadbalancers and then 
associated to Loadbalancers.

-Vijay

From: Samuel Bercovici [mailto:samu...@radware.com]
Sent: Thursday, May 15, 2014 10:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS]LBaaS 1st Session etherpad

Hi,

If a tenant wishes to expose his application (listener, pool(s), etc.) via 
multiple different virtual IP addresses you can do so.

-Sam.

From: Vijay Venkatachalam [mailto:vijay.venkatacha...@citrix.com]
Sent: Thursday, May 15, 2014 12:21 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS]LBaaS 1st Session etherpad

Hi,

I see the following statement in the doc.

>>multiple loadbalancers may referenece the same listener

Does this mean listeners are independent of loadbalancer?

Thanks,
Vijay V.

From: Samuel Bercovici [mailto:samu...@radware.com]
Sent: Thursday, May 15, 2014 9:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][LBaaS]LBaaS 1st Session etherpad

Hi Everyone,

https://etherpad.openstack.org/p/juno-lbaas-design-session

Feel free to modify and update, please make sure you use your name so we will 
know who have added the modification.

Regards,
-Sam.


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [NFV] New Sub-team and Meeting

[Russell Bryant]

It is clear that a number of us have been working independently on NFV
related features.  It would be beneficial to start doing some
coordination in this area.  To do that, I think we should form an NFV
group with a regular IRC meeting.  I'd like to see this group be a
collaboration of developers, deployers, and end users working together
to make sure we are successful in supporting NFV use cases.

Proposed set of goals for this group:

 * Organize documentation on the OpenStack wiki of use cases and gaps to
be filled in OpenStack.

 * Identify relevant development efforts across OpenStack (designs,
code) and track their progress.

   - Provide a page for interested parties to quickly see the status
 across these efforts

   - Highlight areas that need additional help.

 * Provide a meeting where people can get together and discuss this work
   on a regular basis.

To get us started, I have created the following wiki page with some
information on some of the efforts already under way.  I welcome help
filling it in with more details.

https://wiki.openstack.org/wiki/Meetings/NFV

For the IRC meeting, I propose we start meeting in a couple weeks with
the first one on Wednesday, June 4 at 1400 UTC in #openstack-meeting.
It's going to be tough to pick a date/time that works for everyone, but
if this absolutely does not work for you and you'd like to participate,
feedback is welcome.

For discussions outside of the meeting about these features, I think we
should use the openstack-dev mailing list.  When posting about NFV,
please use the [NFV] tag in the message subject.

Thanks!

-- 
Russell Bryant

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] 10:30am today, B203 table 6 for Neutron//Re: Scaling Network Performance for Large Clouds: Thursday May 15th at 10:30-11am in the developer lounge at 3rd floor

[Tina TSOU]

Dear Neutron Stackers,

A kind reminder:

We are setting up a meeting to discuss Scaling Network Performance for Large 
Clouds. There are already cases from eBay, Yahoo, and Huawei customers.

Here is related BP:
https://blueprints.launchpad.net/neutron/+spec/scaling-network-performance


The meeting is planned for:
   Thursday May 15th at 10:30-11am in the B203 table 6 for Neutron

Look forward to talking to many of you then.


Thank you,
Tina

On May 14, 2014, at 10:00 AM, "Tina TSOU" 
mailto:tina.tsou.zout...@huawei.com>> wrote:

Dear all,

Place is changed to B203 table 6 for Networking (Neutron), Design Summit Pod 
area.


Thank you,
Tina

On May 14, 2014, at 8:00 AM, "Tina TSOU" 
mailto:tina.tsou.zout...@huawei.com>> wrote:

Dear Stackers,

Oops, the complete link of that BP should be below.


https://blueprints.launchpad.net/neutron/+spec/scaling-network-performance


Thank you,
Tina

From: Tina TSOU
Sent: Tuesday, May 13, 2014 10:29 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Scaling Network Performance for Large Clouds: Thursday May 15th at 
10:30-11am in the developer lounge at 3rd floor

Dear Stackers,

We are setting up a meeting to discuss Scaling Network Performance for Large 
Clouds. There are already cases from eBay, Yahoo and Huawei customers.

Here is related BP:

https://blueprints.launchpad.net/neutron/+spec/scaling-network-perform

The meeting is planned for:
   Thursday May 15th at 10:30-11am in the developer lounge at 3rd 
floor
Look forward to talking to many of you then.


Thank you,
Tina

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [keystone] [barbican] Protecting user specific secrets in Barbican

[Tiwari, Arvind]

Barbcan will be used as secret store (or Key Manager) in Open Stack 
deployments. That means users can store any kind for secrets (ssh keys , access 
keys, password .) in Barbican these secrets are not shared secrets.

In below scenario it seems secrets are not well protected in Barbican


1.   Barbican in integrated a OS based cloud deployment.

2.   In particular domain there is one (or multiple) project.

3.   Users are associated with the project through role (two coworker can 
have same role e.g. creator) or a admin user have higher role.

4.   Users have their secrets (ssh keys , access keys, password .) for 
services (VMs per users, resources) saved in Barbican.


Problem


1.   Users with the same role or Admin on project can see each other 
secrets which are not a shared secrets.

2.   Multiple projects (or project hierarchy) per user just to store 
secrets is not going to help as it will lead to project exposition and 
confusing. At the same time projects are not meant to go 1 to 1 with user.

3.   Project hierarchy is also not a good solution as user on top of the 
hierarchy (reseller admin) can inherits role and able to steal the secrets.


Note, Barbican is designed for secret storage and protection, we need better 
management on secrets in Barbican. We also need better solution to address this 
problem.


Keystone and Barbican (or interested party) team, can we have a meeting today 
to brainstorm this issue and come up with better solution?


Thanks
Arvind



___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron] Monitoring agent

[Zang MingJie]

Hi All:

I want to know is there any way to continuously monitor ports
connectivity, and report dead port via snmp trap or whatever.

Currently I got neutron-debug utility which can help me checking port
status by hand, but it would be better to have an agent to do the job
automatically, and also collect port statistics for analysis.

Look for suggestion

Regards

--
Zang MingJie

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat]How to get metadata when vm in a network without dhcp?

[Qiming Teng]

Please post usage question to openst...@lists.openstack.org, not this
development mailing list. 
As for your case, you may want to check config_drive, which is supported
both at nova cli and heat templates.

Regards,
  Qimng

On Thu, May 15, 2014 at 05:34:57PM +0800, xuanlangjian wrote:
> Hi guys,
> I'm facing a problem when using heat template, my network has no
> dhcp. So after vm up, I will manually configure a ip for it. But in
> this case, vm can't get metadata scripts, and also can't do any
> configure work.
> So I'm wondering is there a way to get metadata scripts to work
> without IP, or configure IP automatically before getting metadata
> scripts?
> 
> Best Regards,
> Ethan Lynn
> 
 


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron][LBaaS] Updated Object Model?

[Eugene Nikanorov]

Hi Craig,

Implementation-specific options are not exposed through the API, or
otherwise it would be inconsistent, given that we are moving to a
flavor-based approach of specifying service requirements where
implementation is completely hidden from the user.

Thanks,
Eugene.


On Thu, May 15, 2014 at 3:24 AM, IWAMOTO Toshihiro wrote:

> At Wed, 14 May 2014 10:18:29 -0700,
> Stephen Balukoff wrote:
> >
> > [1  ]
> > [1.1  ]
> > Hi Craig,
> >
> > I'm attaching the latest object model diagram as discussed with the RAX
> > team last night, Samuel and Eugene. Note that we don't necessarily have
> > HP's blessing on this model yet, nor do we have Neutron core developer
> buy
> > in.  But in any case, here it is.
>
> Sorry for jumping into a meta-argument,
> but what the LBaaS community needs to do first is to figure out how to
> make the neutron community agree on a LBaaS proposal.
> On the other hand, the neutron community (or the core?) needs to make
> it clear that what criteria or process is required to approve some
> LBaaS idea (obj. model, API, whatsoever).
>
>
> I'm sorry to say (again) that not much people have energy to follow
> and check out small differences in those large pictures of LBaaS
> object models.
>
> --
> IWAMOTO Toshihiro
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [keystone] Service scoped role definition

[David Chadwick]

In preparation for and input to today's design summit session on
Authorisation at 11.50am, I thought it might be beneficial to remind
folks of the proposed design that was circulated by me at the end of the
long discussion on the format of a scoped role, that was held at the end
of last year on this list. Here it is:

 {
 "role": {
  "id": "76e72a",
  "domain_id" = "--id--",(optional, if present, role is named by
specific domain)
  "project_id" = "--id--",(optional, if present, role is named
by project)
  "service_id" = "--id--",(optional, if present, role is named
by service)
  "name": "---role_name---",  (must be unique when combined with
domain, project and service ids)
  "scope": {"id": "---id---", (resource_id)
 "type": "service | file | domain etc.",
 "endpoint":"---endpoint---"
   }
}
 }

regards

David


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [heat]How to get metadata when vm in a network without dhcp?

[xuanlangjian]

Hi guys,
I'm facing a problem when using heat template, my network has no 
dhcp. So after vm up, I will manually configure a ip for it. But in this 
case, vm can't get metadata scripts, and also can't do any configure work.
So I'm wondering is there a way to get metadata scripts to work 
without IP, or configure IP automatically before getting metadata scripts?


Best Regards,
Ethan Lynn

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev