Re: [openstack-dev] [Openstack][Neutron]Why we use secuirity group which only support dispatching whiltelist rules?

[Ihar Hrachyshka]

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

Ihar

On Sun, Apr 23, 2017 at 8:33 PM, 田明明  wrote:
> Can we add an "action" to security group rule api, so that we could dispatch
> rules with "deny" action? Until now， security group only supports add
> white-list rules but this couldn't satisfy many people's needs.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Openstack][Neutron]Why we use secuirity group which only support dispatching whiltelist rules?

[田明明]

Can we add an "action" to security group rule api, so that we could dispatch 
rules with "deny" action? Until now， security group only supports add 
white-list rules but this couldn't satisfy many people's needs.




 





 





 __
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [heat][tripleo] Heat dependency visualisation (an old topic revived)

[Steve Baker]

Could you please try the "--format dot" formatter for the "openstack stack
resource list" command? It may meet your needs now, and I'm sure patches
would be welcome to the dot formatter to control what diagrams get
generated.

On Sat, Apr 22, 2017 at 6:28 AM, Bogdan Dobrelya 
wrote:

> Hello.
>
> [tl;dr] It is hard to read dependencies from the heat templates, for
> humans, without accessing Heat deployed your stacks live. So robots for
> the rescue!
>
> Original topic [0]. Also there is related blog post [1].
> The latter [2] expects your changes under test to be deployed live and
> queries Heat API, IIUC.
>
> While the former [3] can be used "offline" and helps to visualize
> dependency graph *very* fast, but didn't work for me as is (tried with
> tripleo heat templates Ocata).
>
> I reworked it a little bit [4] to fit my needs with t-h-t, which is I
> want to know which things is followed by which another things and so on,
> especially while those things is being changed all the time these days
> of containers and unicorns :)
>
> I hope this reworked tool can as well help other folks who wanted to
> know how tripleo heat templates deployment graph looks like and how to
> move things across that graph w/o troubles and w/o asking too many
> questions to Steven Hardy (like I did initially) haha.
>
> Kudos Alexis and Lars for great tools!
>
> [0] https://goo.gl/ajUMSi
> [1] http://blog.oddbit.com/2014/09/02/visualizing-heat-stacks/
> [2] https://github.com/larsks/dotstack
> [3] https://github.com/lxsli/heat-viz
> [4] https://github.com/bogdando/heat-viz
>
> --
> Best regards,
> Bogdan Dobrelya,
> Irc #bogdando
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] [daisycloud-core]Do we really need to upgrade pbr, docker-py and oslo.utils

[Jeffrey Zhang]

imo, we should follow global requirements restrict and upgrade the package
when
openstack/requirements upgrade it.

several reason.

1. Even if you do not co-install kolla with other project, it also affect
the distro packaging.
   For example RDO package kolla now and we should provide a good
requirements.txt for them.
   And we do not prevent user to co-install kolla with other project too.

2. requirements upgrade may related to vulnerable bug.

3. It is hard to maintain the requirements for kolla with
project/requirements.


On Thu, Apr 20, 2017 at 11:45 AM,  wrote:

> Hello,
>
>
> As global requirements changed in Ocata, Kolla upgrads pbr＞=1.8 [1] ,
>
> docker-py＞=1.8.1[2] . Besides, Kolla also starts depending on
>
> oslo.utils＞=3.18.0 to use uuidutils.generate_uuid() instead of
> uuid.uuid4() to
>
> generate UUID.
>
>
> IMHO, Upgrading of [1] and [2] are actually not what Kolla really need to,
>
> and uuidutils.generate_uuid() is also supported by oslo.utils-3.16. I mean
>
> If we keep Kolla's requirement in Ocata as what it was in Newton, upper
> layer
>
> user of Kolla like daisycloud-core project can still keep other things
> unchanged
>
> to upgrade Kolla from stable/newton to stable/ocata. Otherwise, we have to
>
> upgrade from centos-release-openstack-newton to
>
> centos-release-openstack-ocata(we do not use pip since it conflicts with
> yum
>
> on files installed by same packages). But this kind of upgrade may be too
>
> invasive that may impacts other applications.
>
>
> I know that there were some discusstions about global requirements update
>
> these days. So if not really need to do these upgrades by Kolla itself, can
>
> we just keep the requirement unchanged as long as possible?
>
>
> My 2c.
>
>
> [1] https://github.com/openstack/kolla/commit/
> 2f50beb452918e37dec6edd25c53e407c6e47f53
>
> [2] https://github.com/openstack/kolla/commit/
> 85abee13ba284bb087af587b673f4e44187142da
>
> [3] https://github.com/openstack/kolla/commit/
> cee89ee8bef92914036189d02745c08894a9955b
>
>
>
>
>
>
> B. R.,
>
> Zhijiang
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


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

Re: [openstack-dev] [TripleO][CI] Quickstart deep dive

[Emilien Macchi]

On Sun, Apr 23, 2017 at 3:58 PM, Gabriele Cerami  wrote:
> Hi,
>
> with the end of the first phase of the transition of CI to quickstart,
> it was suggested it could be beneficial to everyone doing a deep dive of
> quickstart, how to use it, how to contribute to it.
> I'm proposing next thursday, 27th of april as the date for such a deep
> dive.

What time?

> The location: https://bluejeans.com/176756457/
> The Agenda: https://etherpad.openstack.org/p/quickstart-deep-dive
> I think we're trying to cover all the needed topic, feel free to add a
> request on the bottom part of the page.
>
> All the informations are stored here
>
> https://etherpad.openstack.org/p/tripleo-deep-dive-topics
>
> Any feedback welcome.

Thanks, this is really cool.
-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] priorities for the current week (04/23-04/27)

[Brian Rosmaita]

1 Pike midcycle review
==
Hopefully, you saw my summary of the Glance Pike virtual midcycle
meeting ... if not, here it is:
- http://lists.openstack.org/pipermail/openstack-dev/2017-April/115777.html


2 Spec finalization
===
I realize that many Glance cores are kind of preoccupied at the moment,
but here are some patches that will be quick to review and can help get
the specs repo cleaned up:
- https://review.openstack.org/#/c/459132/
- https://review.openstack.org/#/c/451560/
- https://review.openstack.org/#/c/206120/
- https://review.openstack.org/#/c/448680/

See this etherpad if you're wondering why we're still messing with some
of the above patches:
https://etherpad.openstack.org/p/glance-pike-specs-review


3 Image import refactor
===
Of course!
- https://review.openstack.org/#/c/391442/
- https://review.openstack.org/#/c/391441/
- https://review.openstack.org/#/c/443636/
- https://review.openstack.org/#/c/443632/
- https://review.openstack.org/#/c/443633/


Have a productive week!
brian

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Affected by OSIC, Layoffs? Or want to help?

[Brian Rosmaita]

As an OSIC casualty, I want to thank Lauren for organizing this.  While
being hit by layoffs is extremely unpleasant, it's really awesome how
supportive the OpenStack community has been--reaching out with job
leads, offering general commiseration, as well as this practical effort
to get us to the Boston Summit.  I like working on OpenStack because we
are tackling challenging problems and producing quality software, but
also because OpenStack is a real community of developers working toward
a common goal.

cheers,
brian

PS: I should give my special thanks to Lauren, I think I may have used
up her frequent flyer miles.


On 4/21/17 12:36 PM, Lauren Sell wrote:
> Hi everyone,
> 
> The Foundation wants to help any Stackers affected by recent layoffs such as 
> OSIC get to the Boston Summit. There are companies hiring and we want to 
> retain our important community members! 
> 
> If you are a contributor who was recently laid off and need help getting to 
> Boston, please contact me ASAP. We have a little bit of room left in our 
> travel support block, and want to extend rooms and free passes to those 
> affected to help if we can.  
> 
> Amy Marrich also had a great idea for any of you frequent flyers interested 
> in pitching in! Community members could offer up some of our personal 
> frequent flyer miles to sponsor flights for these Stackers. I’d love to be 
> the first...if you were laid off and need sponsorship for a flight, I’m 
> willing to sponsor a round trip domestic flight or one-way international 
> flight with my miles. Contact me. 
> 
> Anyone else want to pitch in?
> 
> Cheers,
> Lauren
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [TripleO][CI] Quickstart deep dive

[Gabriele Cerami]

Hi,

with the end of the first phase of the transition of CI to quickstart,
it was suggested it could be beneficial to everyone doing a deep dive of
quickstart, how to use it, how to contribute to it.
I'm proposing next thursday, 27th of april as the date for such a deep
dive.

The location: https://bluejeans.com/176756457/
The Agenda: https://etherpad.openstack.org/p/quickstart-deep-dive
I think we're trying to cover all the needed topic, feel free to add a
request on the bottom part of the page.

All the informations are stored here

https://etherpad.openstack.org/p/tripleo-deep-dive-topics

Any feedback welcome.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [storlets] Proposing a new meeting time for this week

[Eran Rom]

Hi all,
We have not met for quite some time, and unfortunately, I cannot make it this 
week as well.
Any chance Wed April 26th 08:00UTC. works for you as am alternative time.
Otherwise, you can make the meeting without me.

Best,
Eran
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [storlets][mascot] mascot for the storlets project

[Eran Rom]

Hi All,
Any feedbacks?
Personally I like it.

Thanks,
Eran

> Begin forwarded message:
> 
> From: Heidi Joy Tretheway 
> Subject: Re: mascot for the storlets project
> Date: April 22, 2017 at 1:14:27 AM GMT+3
> To: Eran Rom 
> 
> Hi Eran, 
> 
> I took your feedback on the storklet to our illustrators and they came up 
> with this revised version. Would you please let me know what your team 
> thinks? 
> 
> 
>> On Feb 28, 2017, at 11:52 AM, Heidi Joy Tretheway > > wrote:
>> 
>> Hi Eran, 
>> 
>> Thank you so much! These are great pictures to give me an idea of what a 
>> stork let should look like. I’ll share both with our illustration team. 
>> 
>> Best,
>> Heidi Joy
>> 
>>> On Feb 28, 2017, at 11:43 AM, Eran Rom >> > wrote:
>>> 
>>> Heidi Hi,
>>> In the PTG our team has chose ’storklet’ as a mascot.
>>> I was not aware until recently that there is such a word, and that it is 
>>> the stork chick.
>>> 
>>> Here is a couple of nice stoklet pictures I have found:
>>> http://www.arkive.org/marabou-stork/leptoptilos-crumeniferus/image-G69355.html
>>>  
>>> 
>>>  (A marabou storklet )
>>> http://www.daufuskieislandconservancy.org/index.php?page=wood-stork 
>>>  (A 
>>> wood stork storklet)
>>> 
>>> Thanks very much!
>>> Eran
>>> 
>> 
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

[Matt Riedemann]

On 4/23/2017 10:13 AM, Matt Riedemann wrote:


Yikes, I'm going to need help with Nova and anything that predates the
v2.0 API. I think there was a 1.1 at some point? Which means there was a
1.0? Does anyone know at what point 2.0 was created? I didn't start
working on OpenStack until ~Folsom.

I can dig as well as anybody, but was just wondering if anyone knows off
the top of their head.



Nevermind, I think I got it:

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

That was a fun trip down memory lane. You know it's bad when you have to 
download a tar ball from launchpad to find the austin release code.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][ptls][tc] help needed filling out project-navigator data

[Matt Riedemann]

On 4/19/2017 9:54 AM, Jimmy McArthur wrote:

Ideally, as far back as your project goes. That way we will have a
complete API history, per release, on the project navigator.  This also
helps us determine the project age.

Thanks!
Jimmy



Yikes, I'm going to need help with Nova and anything that predates the 
v2.0 API. I think there was a 1.1 at some point? Which means there was a 
1.0? Does anyone know at what point 2.0 was created? I didn't start 
working on OpenStack until ~Folsom.


I can dig as well as anybody, but was just wondering if anyone knows off 
the top of their head.


--

Thanks,

Matt

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [oslo] do we still need non-voting tests for older releases?

[ChangBo Guo]

>From operator and user view,  we just make sure  same stable branch of oslo
and other service work well .
So I think we don't need these jobs anymore, would like to get more input
from others

2017-04-21 23:37 GMT+08:00 Doug Hellmann :

> Excerpts from ChangBo Guo's message of 2017-04-21 16:04:35 +0800:
> > What the related thing I can remember is we discuss oslo libraries'
> > compatibility in [1], which was abandoned.
> > I made stable compat ocata jobs non-voting in [2], hope can revert when
> > related bug is fixed before.
> > But now, If we decide remove them, we don't revert anymore.
>
> With our constraint system and with stable branches for libraries,
> do we need new releases from master to be compatible with older
> services on stable branches?
>
> Doug
>
> >
> > [1]  https://review.openstack.org/226157
> > [2]  https://review.openstack.org/#/c/448431
> >
> > 2017-04-20 0:42 GMT+08:00 Doug Hellmann :
> >
> > > I noticed again today that we have some test jobs running for some
> > > of the Oslo libraries against old versions of services (e.g.,
> > > gate-tempest-dsvm-neutron-src-oslo.log-ubuntu-xenial-newton,
> > > gate-tempest-dsvm-neutron-src-oslo.log-ubuntu-xenial-ocata, and
> > > gate-oslo.log-src-grenade-dsvm-ubuntu-xenial-nv).
> > >
> > > I don't remember what those are for, but I imagine they have to do
> > > with testing compatibility. They're all non-voting, though, so maybe
> > > not?
> > >
> > > Now that we're constraining libraries in our test systems, I wonder
> > > if we still need the jobs at all?
> > >
> > > Doug
> > >
> > > 
> __
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
ChangBo Guo(gcb)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Trinath Somanchi]

Thanks a lot for these workshop sessions. Looking forward for attending them.

Thanks,
Trinath Somanchi.

Digital Networking | NXP – Hyderabad – INDIA.
Email: trinath.soman...@nxp.com
Mobile: +91 9866235130 | Off: +91 4033504051


From: Steven Dake (stdake) [mailto:std...@cisco.com]
Sent: Sunday, April 23, 2017 6:30 AM
To: OpenStack Development Mailing List (not for usage questions) 

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

As proposed earlier on the mailing list, A 2 week 6 session workshop has been 
organized From April 25th – May 4th Tu/W/Th for 45 minutes in length.

The agenda for this workshop is as follows:

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

Connection details are below:

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

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

Regards
-stevve

OpenStack Kolla-Kubernetes Workshop: Demystifying the Gate

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

17:00 UTC | 45 minutes

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


Meeting number:

202 310 134

Meeting password:

openstack (67367822 from phones)



Join by phone

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

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

Access code: 202 310 134

Global call-in 
numbers
  |  Toll-free calling 
restrictions





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



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev