Re: [Openstack-operators] [Glance] Default policy in policy.json

[Michael Richardson]

On Fri, 17 Jun 2016 16:27:54 +

> Also which would be preferred "role:admin" or "!"? Brian points out on [1] 
> that "!" would in effect, notify the admins that a policy is not defined as 
> they would be unable to preform the action themselves.

+1 for "!" (and brilliant that the Glance project are being proactive on this 
front; hopefully the others will follow suit).

Cheers,
Michael Richardson.

> 
> 
> Thanks,
> 
> Niall
> 
> 
> 1. https://review.openstack.org/#/c/330443/
> 
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


-- 
Michael Richardson
Catalyst IT Limited
150-154 Willis Street, PO Box 11-053 Wellington New Zealand
DDI: ++64 4 803 2260
http://catalyst.net.nz
GPG: 0530 4686 F996 4E2C 5DC7 6327 5C98 5EED A302 

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

Re: [Openstack-operators] DNS searchdomains for your instances?

[Kris G. Lindgren]

Yea we set the DNS servers per network as well.  I am actually asking about the 
search domain, IE what FQDN's should be appended to non-fqdn queries, to a 
lookup the ip of a short name.

IE: if searching for the shortname of: somevm.  If you had a search domain of 
domain1.com, domain2.net, and domain3.org – it would try each of those domain 
names in order until it found: somevm..
___
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

From: > on behalf of David 
Medberry >
Date: Monday, June 20, 2016 at 1:19 PM
To: "Kris G. Lindgren" >
Cc: "openstack-oper." 
>
Subject: Re: [Openstack-operators] DNS searchdomains for your instances?

and of course that was the WRONG picture

https://www.dropbox.com/s/wxe9e9nu5cqgx9m/Screenshot%202016-06-20%2013.17.02.png?dl=0

On Mon, Jun 20, 2016 at 1:18 PM, David Medberry 
> wrote:
Each tenant in our neutron network has their own subnet and each subnet sets 
its own dns rules (see pic).

https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0

On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren 
> wrote:
Hello all,

Wondering how you guys are handling the dns searchdomains for your instances in 
your internal cloud.  Currently we are updating the network metadata template, 
on each compute node,  to include the dns-search-domains options.  We (Josh 
Harlow) is working on implement the new network template that nova created (in 
liberty) and are trying to get this added.  Currently nova/neutron doesn't 
support any option to specify this metadata/information anywhere.  I see some 
work on the neutron side to allow setting of extra dhcp-opts network wide 
(currently only allowed on a port) [1] [2].  But once that gets merged, then 
changes need to be made on the nova side to pull that extra data into the 
network.json.

So that begs the question how are other people handling this?

[1] (spec) - https://review.openstack.org/#/c/247027/
[2] (code) - https://review.openstack.org/#/c/248931/

___
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy

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



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

Re: [Openstack-operators] DNS searchdomains for your instances?

[David Medberry]

and of course that was the WRONG picture

https://www.dropbox.com/s/wxe9e9nu5cqgx9m/Screenshot%202016-06-20%2013.17.02.png?dl=0

On Mon, Jun 20, 2016 at 1:18 PM, David Medberry 
wrote:

> Each tenant in our neutron network has their own subnet and each subnet
> sets its own dns rules (see pic).
>
> https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0
>
> On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren 
> wrote:
>
>> Hello all,
>>
>> Wondering how you guys are handling the dns searchdomains for your
>> instances in your internal cloud.  Currently we are updating the network
>> metadata template, on each compute node,  to include the dns-search-domains
>> options.  We (Josh Harlow) is working on implement the new network template
>> that nova created (in liberty) and are trying to get this added.  Currently
>> nova/neutron doesn't support any option to specify this
>> metadata/information anywhere.  I see some work on the neutron side to
>> allow setting of extra dhcp-opts network wide (currently only allowed on a
>> port) [1] [2].  But once that gets merged, then changes need to be made on
>> the nova side to pull that extra data into the network.json.
>>
>> So that begs the question how are other people handling this?
>>
>> [1] (spec) - https://review.openstack.org/#/c/247027/
>> [2] (code) - https://review.openstack.org/#/c/248931/
>>
>> ___
>> Kris Lindgren
>> Senior Linux Systems Engineer
>> GoDaddy
>>
>> ___
>> OpenStack-operators mailing list
>> OpenStack-operators@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] DNS searchdomains for your instances?

[David Medberry]

Each tenant in our neutron network has their own subnet and each subnet
sets its own dns rules (see pic).

https://www.dropbox.com/s/dgfgkdqijmrfweo/2016-06-19%2005.15.29.jpg?dl=0

On Mon, Jun 20, 2016 at 1:07 PM, Kris G. Lindgren 
wrote:

> Hello all,
>
> Wondering how you guys are handling the dns searchdomains for your
> instances in your internal cloud.  Currently we are updating the network
> metadata template, on each compute node,  to include the dns-search-domains
> options.  We (Josh Harlow) is working on implement the new network template
> that nova created (in liberty) and are trying to get this added.  Currently
> nova/neutron doesn't support any option to specify this
> metadata/information anywhere.  I see some work on the neutron side to
> allow setting of extra dhcp-opts network wide (currently only allowed on a
> port) [1] [2].  But once that gets merged, then changes need to be made on
> the nova side to pull that extra data into the network.json.
>
> So that begs the question how are other people handling this?
>
> [1] (spec) - https://review.openstack.org/#/c/247027/
> [2] (code) - https://review.openstack.org/#/c/248931/
>
> ___
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> ___
> OpenStack-operators mailing list
> OpenStack-operators@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] DNS searchdomains for your instances?

[Kris G. Lindgren]

Hello all,

Wondering how you guys are handling the dns searchdomains for your instances in 
your internal cloud.  Currently we are updating the network metadata template, 
on each compute node,  to include the dns-search-domains options.  We (Josh 
Harlow) is working on implement the new network template that nova created (in 
liberty) and are trying to get this added.  Currently nova/neutron doesn't 
support any option to specify this metadata/information anywhere.  I see some 
work on the neutron side to allow setting of extra dhcp-opts network wide 
(currently only allowed on a port) [1] [2].  But once that gets merged, then 
changes need to be made on the nova side to pull that extra data into the 
network.json.

So that begs the question how are other people handling this?

[1] (spec) - https://review.openstack.org/#/c/247027/
[2] (code) - https://review.openstack.org/#/c/248931/

___
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Ops Meetups Team - Meeting Tuesday 1400 UTC (mid-cycle venue selection!)

[Jonathan Proulx]

This means <24hr to add your choice to the non binding doodle poll:

http://doodle.com/poll/e4heruzps4g94syf

Venue details recored here:

https://etherpad.openstack.org/p/ops-meetup-venue-discuss

And of course if you are available to join us tomorrow at 1400UTC
please do 

-Jon

On Mon, Jun 20, 2016 at 12:26:07PM +0800, Tom Fifield wrote:
:
:Hi all,
:
:We're having a special meeting:
:
:Tuesday, 21 of Jun at 1400 UTC [1]
:
:where we will decide the venue for the next mid-cycle will be!
:
:See you in IRC[2], in the #openstack-operators channel.
:
:
:Details about the group, and the link to the agenda etherpad, can be
:found at:
:
:https://wiki.openstack.org/wiki/Ops_Meetups_Team#Meeting_Information
:
:
:
:Regards,
:
:
:Tom
:
:
:[1] To see this in your local time - check: 
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Ops+Meetups+Team=20160621T14
:
:[2] If you're new to IRC, there's a great guide here:
:http://docs.openstack.org/upstream-training/irc.html
:
:___
:OpenStack-operators mailing list
:OpenStack-operators@lists.openstack.org
:http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-- 

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

[Openstack-operators] DRAFT: OpenStack UX Personas

[Caballero Abraham, Rodrigo]

Hello,

I am happy to share my preliminary work on the OpenStack UX Personas.

You can find the approved spec for this content here:
https://review.openstack.org/#/c/309567/2/specs/newton/ux-personas.rst

The actual Gerrit change with the early draft is found here:
https://review.openstack.org/#/c/326662/

I am looking forward to your feedback so that I can improve the content as much 
as possible.

Regards,

Rodrigo Caballero

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