Re: [openstack-dev] [Designate] DNS Services PTL Candidacy

On 09/23/2014 05:11 AM, Mac Innes, Kiall wrote: Hi all, I'd like to announce my candidacy for the DNS Services Program PTL position. I’ve been involved in Designate since day one, as the both original author and as pseudo-PTL pre-incubation. Designate and the DNS Services program have

[openstack-dev] Introduction: Rich Megginson - Designate project

Hello. My name is Rich Megginson. I am a Red Hat employee interested in working on Designate (DNSaaS), primarily in the areas of integration with IPA DNS, DNSSEC, and authentication (Keystone). I've signed up for the openstack/launchpad/gerrit accounts. Be seeing you (online

[openstack-dev] [designate] Workshop Summary - Austin, TX January 2014

Designate (OpenStack DNSaaS) Workshop - Austin, TX - January 27-29, 2014 hosted by Rackspace = Development Process Review = Adrian Otto gave an overview of the Solum development process. One interesting idea is to keep commits posted for review small, under 200 lines, to ease reviews and

Re: [openstack-dev] [devstack][keystone] (98)Address already in use: make_sock: could not bind to address [::]:5000 0.0.0.0:5000

On 07/16/2014 08:43 AM, Brian Haley wrote: On 07/16/2014 07:34 AM, Joe Jiang wrote: Hi all, When I just set up my develope environment use devstack at CentOS 6.5, that fetch devstack source via github.com and checkout stable/icehouse branch. and bellow[1] is the error log fragment. I'm not

Re: [openstack-dev] [devstack][keystone] (98)Address already in use: make_sock: could not bind to address [::]:5000 0.0.0.0:5000

On 07/16/2014 09:10 AM, Morgan Fainberg wrote: -- From: Rich Megginson rmegg...@redhat.com Reply: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: July 16, 2014 at 08:08:00 To: openstack-dev

Re: [openstack-dev] [devstack][keystone] (98)Address already in use: make_sock: could not bind to address [::]:5000 0.0.0.0:5000

On 07/16/2014 10:40 PM, Joe Jiang wrote: Hi all, Thanks for your responds. I try to running # sudo semanage port -l|grep 5000 in my envrionment and get same infomation. ... commplex_main_port_t tcp 5000 commplex_main_port_t udp 5000 then, I wanna remove this port(5000) from SELinux policy

Re: [openstack-dev] [Neutron][Nova][Designate][L3][IPv6] Discussion about Cross-Project Integration of DNS at Summit

On 04/29/2014 06:59 PM, Collins, Sean wrote: Count me in! +1 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [designate] sink listeners for fixed and floating IP addresses

designate-sink currently ships with a nova_fixed handler, which listens for nova events compute.instance.create.end and compute.instance.delete.start, and a neutron_floatingip for events floatingip.update.end and floatingip.delete.start. 1) is it correct to say that nova_fixed is for internal

Re: [openstack-dev] [Designate] Core reviewer update

On 02/12/2015 08:51 AM, Hayes, Graham wrote: On 12/02/15 15:50, Kiall Mac Innes wrote: +1 - Tim has been giving good reviews over the last few months and will make a good addition.. Thanks, Kiall On 12/02/15 15:40, Vinod Mangalpally wrote: Hello Designate folks, Betsy Luzader (betsy)

Re: [openstack-dev] [Keystone] Requesting FFE for last few remaining patches for domain configuration SQL support

On 03/17/2015 01:26 PM, Henry Nash wrote: Hi Prior to Kilo, Keystone supported the ability for its Identity backends to be specified on a domain-by-domain basis - primarily so that different domains could be backed by different LDAP servers. In this previous support, you defined the

Re: [openstack-dev] HTTPD Config

On 03/06/2015 12:37 AM, Matthias Runge wrote: On 05/03/15 19:49, Adam Young wrote: I'd like to drop port 5000 all-together, as we are using a port assigned to a different service. 35357 is also problematic as it is in the middle of the Ephemeral range. Since we are talking about running

Re: [openstack-dev] Problem about Juno Keystone Identity V3

On 04/03/2015 09:09 AM, Amy Zhang wrote: Hi guys, I have done switching Keystone Identity V2 to V3 in Icehouse and it works perfect. However, I use the same way to switch Keystone Identity V2 to V3 in Juno, it doesn't work. It give me the error: ERROR: openstack Internal Server Error (HTTP

Re: [openstack-dev] [puppet] Status of Beaker jobs

On 05/01/2015 05:35 PM, Emilien Macchi wrote: Hi, TL;DR: Please review: https://review.openstack.org/#/q/status:open++topic:bug-1444736,n,z I would like to share some progress/feedback about integrating Beaker in our modules. First, everything is updated in the Google Doc [1] My main

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 05/04/2015 06:03 PM, Mathieu Gagné wrote: On 2015-05-04 7:35 PM, Rich Megginson wrote: The way authentication works with the Icehouse branch is that puppet-keystone reads the admin_token and admin_endpoint from /etc/keystone/keystone.conf and passes these to the keystone command via

Re: [openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

On 05/04/2015 07:52 PM, Mathieu Gagné wrote: On 2015-05-04 9:15 PM, Rich Megginson wrote: On 05/04/2015 06:03 PM, Mathieu Gagné wrote: On 2015-05-04 7:35 PM, Rich Megginson wrote: The way authentication works with the Icehouse branch is that puppet-keystone reads the admin_token

Re: [openstack-dev] [puppet] Proposal to configure Oslo libraries

On 05/08/2015 07:17 AM, Doug Hellmann wrote: Excerpts from Ben Nemec's message of 2015-05-07 15:57:48 -0500: I don't know much about the puppet project organization so I won't comment on whether 1 or 2 is better, but a big +1 to having a common way to configure Oslo opts. Consistency of those

[openstack-dev] [puppet][operators] How to specify Keystone v3 credentials?

I'm currently working on Keystone v3 support in the openstack puppet modules. The way authentication works with the Icehouse branch is that puppet-keystone reads the admin_token and admin_endpoint from /etc/keystone/keystone.conf and passes these to the keystone command via the

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

On 05/05/2015 12:20 PM, Colleen Murphy wrote: I'm cross-posting to the dev list since this conversation should be happening there and is related to another thread there. Ok. I'm not replying puppet-openstack. I'm going to top-post a summary and then respond inline. The summary so far is

Re: [openstack-dev] Problem about Juno Keystone Identity V3

*From:* Rich Megginson [rmegg...@redhat.com] *Sent:* Friday, April 03, 2015 10:52 AM *To:* openstack-dev@lists.openstack.org *Subject:* Re: [openstack-dev] Problem about Juno Keystone Identity V3 On 04/03/2015 09:09 AM, Amy Zhang wrote: Hi guys, I have done switching

Re: [openstack-dev] Kilo v3 identity problems

On 06/03/2015 10:29 AM, Amy Zhang wrote: Hi guys, I have installed Kilo and try to use identity v3. I am using v3 policy file. I changed the domain_id for cloud admin as default. As cloud admin, I tried openstack domain list and got the error message saying that I was not authorized. The

[openstack-dev] [puppet] stubs considered harmful in spec tests

Summary - In puppet module spec tests, do not use stubs, which means the method will be called 0 or more times. Instead, use expects, which means the method must be called exactly 1 time, or some other more fine grained expectation method stubber. Our puppet unit tests mostly use rspec, but

Re: [openstack-dev] [Keystone][OSC] Keystone v3 user create --project $projid does not add user to project?

this has changed, I had to work around it, by making the puppet-keystone user create function also add the user to the project. https://review.openstack.org/#/c/174976/24/lib/puppet/provider/keystone_user/openstack.rb Cheers, Raildo Mascena On Tue, Jun 16, 2015 at 1:52 PM Rich Megginson

[openstack-dev] [puppet][keystone] How to uniquely name Keystone v3 resources in puppet?

The problem with puppet-keystone and Keystone v3 domains is naming of puppet resources contained within domains - users, groups, projects. Suppose you have an admin user in domain dom1 and an admin user in domain dom2. How do you declare these in puppet? You can't do keystone_user {

[openstack-dev] [Keystone][OSC] Keystone v3 user create --project $projid does not add user to project?

Using admin token credentials with the Keystone v2.0 API and the openstackclient, doing this: # openstack project create bar --enable # openstack user create foo --project bar --enable ... The user will be added to the project. Using admin token credentials with the Keystone v3 API and the

[openstack-dev] [keystone][puppet] Federation using ipsilon

I've done a first pass of setting up a puppet module to configure Keystone to use ipsilon for federation, using https://github.com/richm/puppet-apache-auth-mods, and a version of ipsilon-client-install with patches https://fedorahosted.org/ipsilon/ticket/141 and

Re: [openstack-dev] [keystone][puppet] Federation using ipsilon

On 06/12/2015 07:30 PM, Adam Young wrote: On 06/12/2015 04:53 PM, Rich Megginson wrote: I've done a first pass of setting up a puppet module to configure Keystone to use ipsilon for federation, using https://github.com/richm/puppet-apache-auth-mods, and a version of ipsilon-client-install

Re: [openstack-dev] [puppet] Re: Puppet-OpenStack API providers - Follow up

On 05/20/2015 12:17 AM, Gilles Dubreuil wrote: Hi, Just wanted to add, for clarification, the need to restructure the openstacklib. The use of resource[:auth] parameter is causing the providers to behave differently depending on the context, as expressed earlier in this thread. I would to

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

On 08/13/2015 12:41 AM, Gilles Dubreuil wrote: Hi Matthew, On 11/08/15 01:14, Rich Megginson wrote: On 08/10/2015 07:46 AM, Matthew Mosesohn wrote: Sorry to everyone for bringing up this old thread, but it seems we may need more openstackclient/keystone experts to settle this. I'm referring

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

On 07/30/2015 08:53 AM, Matthew Mosesohn wrote: Hi Rich, Sorry, I meant to link [0] to https://bugs.launchpad.net/keystone/+bug/1470635 More responses inline. On Thu, Jul 30, 2015 at 5:38 PM, Rich Megginson rmegg...@redhat.com wrote: There is a patch upstream[1] that enables V3 service

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

On 07/30/2015 08:24 AM, Matthew Mosesohn wrote: Hi all, It seems that I've reached an impasse with https://review.openstack.org/#/q/topic:bp/detach-components-from-controllers,n,z in Keystone with regards to Kilo puppet manifests. One of the objectives is the ability to deploy Keystone on a

Re: [openstack-dev] [devstack][neutron] How to give nested VM access to outside network?

On 08/03/2015 10:07 PM, Rich Megginson wrote: I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a static IP address (because dhcp was not working): cat /etc/sysconfig/network-scripts/ifcfg-eth0 EOF DEVICE=eth0 BOOTPROTO=static DHCPCLASS= HWADDR=$VM_MAC IPADDR=192.168.122.5

[openstack-dev] [devstack][neutron] How to give nested VM access to outside network?

I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a static IP address (because dhcp was not working): cat /etc/sysconfig/network-scripts/ifcfg-eth0 EOF DEVICE=eth0 BOOTPROTO=static DHCPCLASS= HWADDR=$VM_MAC IPADDR=192.168.122.5 NETMASK=255.255.255.0 GATEWAY=192.168.122.1

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

On 07/31/2015 07:18 AM, Matthew Mosesohn wrote: Jesse, thanks for raising this. Like you, I should just track upstream and wait for full V3 support. I've taken the quickest approach and written fixes to puppet-openstacklib and puppet-keystone: https://review.openstack.org/#/c/207873/

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

. On Thu, Jul 30, 2015 at 6:14 PM, Rich Megginson rmegg...@redhat.com wrote: On 07/30/2015 08:53 AM, Matthew Mosesohn wrote: Hi Rich, Sorry, I meant to link [0] to https://bugs.launchpad.net/keystone/+bug/1470635 More responses inline. On Thu, Jul 30, 2015 at 5:38 PM, Rich Megginson rmegg

Re: [openstack-dev] [devstack][neutron] How to give nested VM access to outside network?

, feel free to ask again! [1] https://ask.openstack.org/en/question/44266/connect-vm-in-devstack-to-external-network/ On Mo, 2015-08-03 at 22:07 -0600, Rich Megginson wrote: I'm running devstack in a VM (Fedora 21 host, EL 7.1.x VM) with a static IP address (because dhcp was not working

Re: [openstack-dev] [puppet][keystone] To always use or not use domain name?

On 08/05/2015 07:48 PM, Gilles Dubreuil wrote: On 06/08/15 10:16, Jamie Lennox wrote: - Original Message - From: Adam Young ayo...@redhat.com To: openstack-dev@lists.openstack.org Sent: Thursday, August 6, 2015 1:03:55 AM Subject: Re: [openstack-dev] [puppet][keystone] To always use

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

, Gilles Dubreuil gil...@redhat.com mailto:gil...@redhat.com wrote: On 14/08/15 20:45, Gilles Dubreuil wrote: On 13/08/15 23:29, Rich Megginson wrote: On 08/13/2015 12:41 AM, Gilles Dubreuil wrote: Hi Matthew, On 11/08/15 01:14, Rich Megginson wrote

Re: [openstack-dev] [Fuel][Puppet] Keystone V2/V3 service endpoints

undetected for so long. And since this is supported, we need tests for this. If anyone can speak up on these items, it could help influence the outcome of this patch. Thank you for your time. Best Regards, Matthew Mosesohn On Fri, Jul 31, 2015 at 6:32 PM, Rich Megginson rmegg...@redhat.com

Re: [openstack-dev] [puppet][keystone] To always use or not use domain name?

On 08/10/2015 10:45 AM, Richard Raseley wrote: On 08/07/2015 01:58 PM, Rich Megginson wrote: Would someone who actually has to deploy/maintain puppet manifests and supporting code chime in here? How do you feel about having to ensure that every domain scoped Keystone resource name must end

Re: [openstack-dev] [puppet] Proposing Yanis Guenane core

On 07/27/2015 01:06 PM, Emilien Macchi wrote: Puppet group, Yanis has been working in our group for a while now. He has been involved in a lot of tasks, let me highlight some of them: * Many times, involved in improving consistency across our modules. * Strong focus on data binding, backward

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 10/22/2015 11:09 PM, Gilles Dubreuil wrote: On 21/10/15 00:56, Sofer Athlan-Guyot wrote: Gilles Dubreuil writes: On 14/10/15 17:15, Gilles Dubreuil wrote: On 14/10/15 10:36, Colleen Murphy wrote: On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin

Re: [openstack-dev] [puppet] Creating puppet-keystone-core and proposing Richard Megginson core-reviewer

On 10/31/2015 08:55 AM, Emilien Macchi wrote: At the Summit we discussed about scaling-up our team. We decided to investigate the creation of sub-groups specific to our modules that would have +2 power. I would like to start with puppet-keystone: https://review.openstack.org/240666 And

Re: [openstack-dev] [puppet] WARNING - breaking backwards compatibility in puppet-keystone

was allowed if it was unique among all domains. That code will need to change to specify the domain. Any other code that was already using domains (which I'm assuming is hardly any, if at all) will also need to change. On Oct 7, 2015 10:35 AM, "Rich Megginson" <rmegg.

[openstack-dev] [puppet] WARNING - breaking backwards compatibility in puppet-keystone

tl;dr You must specify a domain when using domain scoped resources. If you are using domains with puppet-keystone, there is a proposed patch that will break backwards compatibility. https://review.openstack.org/#/c/226624/ Replace indirection calls "Indirection calls are replaced with

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 10/07/2015 09:08 AM, Sofer Athlan-Guyot wrote: Rich Megginson <rmegg...@redhat.com> writes: On 10/06/2015 02:36 PM, Sofer Athlan-Guyot wrote: Rich Megginson <rmegg...@redhat.com> writes: On 09/30/2015 11:43 AM, Sofer Athlan-Guyot wrote: Gilles Dubreuil <gil...@red

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 10/13/2015 07:13 AM, Vladimir Kuklin wrote: Puppetmaster and Fuelers, Last week I mentioned that I would like to bring the theme of using native ruby OpenStack client and use it within the providers. Emilien told me that I had already been late and the decision was made that

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

ill speed up puppet runs. But it is not obvious how much that speed up will be, and it is not obvious about the cost of that vs. the current code, and cost/performance vs. using openstackclient in "persistent" mode. On Tue, Oct 13, 2015 at 5:18 PM, Rich Megginson <rmegg...@redhat

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 10/13/2015 09:22 AM, Clayton O'Neill wrote: I agree that ideally, using a native ruby library would be better, but I also share Matt's concern. We'd need a commitment from more than one person to maintain the library if we went that route. I think the big advantages I see with the ruby

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 10/06/2015 02:36 PM, Sofer Athlan-Guyot wrote: Rich Megginson <rmegg...@redhat.com> writes: On 09/30/2015 11:43 AM, Sofer Athlan-Guyot wrote: Gilles Dubreuil <gil...@redhat.com> writes: On 30/09/15 03:43, Rich Megginson wrote: On 09/28/2015 10:18 PM, Gilles Dubreuil wrote:

Re: [openstack-dev] [puppet][Fuel] OpenstackLib Client Provider Better Exception Handling

On 10/13/2015 12:57 PM, Emilien Macchi wrote: On 10/08/2015 07:38 AM, Vladimir Kuklin wrote: [...] * Proposed solution Introduce a library of exception handling methods which should be the same for all puppet openstack providers as these exceptions seem to be generic. Then, for each of the

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 10/13/2015 01:49 PM, Dean Troyer wrote: On Tue, Oct 13, 2015 at 10:33 AM, Rich Megginson <rmegg...@redhat.com <mailto:rmegg...@redhat.com>> wrote: I think if we did end up using a ruby library, we'd also want to make sure it was not only vendored, but also usable i

Re: [openstack-dev] [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

On 08/27/2015 07:00 AM, Gilles Dubreuil wrote: On 27/08/15 22:40, Gilles Dubreuil wrote: On 27/08/15 16:59, Gilles Dubreuil wrote: On 26/08/15 06:30, Rich Megginson wrote: This concerns the support of the names of domain scoped Keystone resources (users, projects, etc.) in puppet

Re: [openstack-dev] [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

To close this thread: http://lists.openstack.org/pipermail/openstack-dev/2015-August/072878.html puppet-openstack will support Keystone domain scoped resource names without a '::domain' in the name, only if the 'default_domain_id' parameter in Keystone has _not_ been set. That is, if the

[openstack-dev] correction: Re: [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

Slight correction below: On 09/01/2015 10:56 AM, Rich Megginson wrote: To close this thread: http://lists.openstack.org/pipermail/openstack-dev/2015-August/072878.html puppet-openstack will support Keystone domain scoped resource names without a '::domain' in the name, only

[openstack-dev] [puppet][keystone] plan for domain name handling

This is to outline the plan for the implementation of "puppet-openstack will support Keystone domain scoped resource names without a '::domain' in the name, only if the 'default_domain_id' parameter in Keystone has _not_ been set. That is, if the default domain is 'Default'." Details here:

[openstack-dev] [puppet][keystone] Keystone resource naming with domain support - no '::domain' if 'Default'

This concerns the support of the names of domain scoped Keystone resources (users, projects, etc.) in puppet. At the puppet-openstack meeting today [1] we decided that puppet-openstack will support Keystone domain scoped resource names without a '::domain' in the name, only if the

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/14/2015 03:26 PM, Sofer Athlan-Guyot wrote: Rich Megginson <rmegg...@redhat.com> writes: I think we could support both. I don't see it as an either/or situation. +1 A. I think it's the B: meaningless approach here. Pros - Easier names That's subjective, creating

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/14/2015 02:30 PM, Sofer Athlan-Guyot wrote: Hi, Gilles Dubreuil writes: A. The 'composite namevar' approach: keystone_tenant {'projectX::domainY': ... } B. The 'meaningless name' approach: keystone_tenant {'myproject': name='projectX', domain=>'domainY',

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/11/2015 01:03 AM, Gilles Dubreuil wrote: Hi, Today in the #openstack-puppet channel a discussion about the pro and cons of using domain parameter for Keystone V3 has been left opened. The context Domain names are needed in Openstack Keystone V3 for identifying users or

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/11/2015 04:17 AM, David Chadwick wrote: Whichever approach is adopted you need to consider the future and the longer term objective of moving to fully hierarchical names. I believe the current Keystone approach is only an interim one, as it only supports partial hierarchies. Fully

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/30/2015 11:43 AM, Sofer Athlan-Guyot wrote: Gilles Dubreuil <gil...@redhat.com> writes: On 30/09/15 03:43, Rich Megginson wrote: On 09/28/2015 10:18 PM, Gilles Dubreuil wrote: On 15/09/15 19:55, Sofer Athlan-Guyot wrote: Gilles Dubreuil <gil...@redhat.com> writes: On 15

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/28/2015 10:18 PM, Gilles Dubreuil wrote: On 15/09/15 19:55, Sofer Athlan-Guyot wrote: Gilles Dubreuil <gil...@redhat.com> writes: On 15/09/15 06:53, Rich Megginson wrote: On 09/14/2015 02:30 PM, Sofer Athlan-Guyot wrote: Hi, Gilles Dubreuil <gil...@redhat.co

Re: [openstack-dev] [puppet][keystone] Choose domain names with 'composite namevar' or 'meaningless name'?

On 09/16/2015 02:58 PM, Cody Herriges wrote: I wrote my first composite namevar type a few years and ago and all the magic is basically a single block of code inside the type... https://github.com/puppetlabs/puppetlabs-java_ks/blob/master/lib/puppet/type/java_ks.rb#L145-L169 It basically boils

Re: [openstack-dev] [puppet] proposing Cody Herriges part of Puppet OpenStack core

On 12/08/2015 09:49 AM, Emilien Macchi wrote: Hi, Back in "old days", Cody was already core on the modules, when they were hosted by Puppetlabs namespace. His contributions [1] are very valuable to the group: * strong knowledge on Puppet and all dependencies in general. * very helpful to debug

Re: [openstack-dev] [puppet] proposing Sofer Athlan Guyot part of puppet-keystone core team

On 12/03/2015 01:05 PM, Emilien Macchi wrote: Hi, For some months, Puppet OpenStack group has been very lucky to have Sofer working with us. He became a huge contributor to puppet-keystone, he knows the module perfectly and wrote insane amount of code recently, to bring new features that our

Re: [openstack-dev] [nova] build_instance pre hook cannot set injected_files for new instance

On 11/19/2015 10:34 AM, Rich Megginson wrote: I have some code that uses the build_instance pre hook to set injected_files in the new instance. With the kilo code, the argv[7] was passed as [] - so I could append/extend this value to add more injected_files. With the latest code

[openstack-dev] [nova] build_instance pre hook cannot set injected_files for new instance

I have some code that uses the build_instance pre hook to set injected_files in the new instance. With the kilo code, the argv[7] was passed as [] - so I could append/extend this value to add more injected_files. With the latest code, this is passed as None, so I can't set it. How can I

Re: [openstack-dev] [puppet] Discussion of PuppetOpenstack Project abbreviation

On 06/03/2016 01:34 AM, Sergii Golovatiuk wrote: I would vote for POSM - "Puppet OpenStack Modules" +1 - possum, american slang for the animal "opossum" -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Jun 1, 2016 at 7:25 PM, Cody Herriges

Re: [openstack-dev] [nova] nova hooks - document & test or deprecate?

On 02/29/2016 12:19 PM, Chris Friesen wrote: On 02/29/2016 12:22 PM, Daniel P. Berrange wrote: There's three core scenarios for hooks 1. Modifying some aspect of the Nova operation 2. Triggering an external action synchronously to some Nova operation 3. Triggering an external action

Re: [openstack-dev] [TripleO] FreeIPA integration

On 04/05/2016 07:06 PM, Dan Prince wrote: On Sat, 2016-04-02 at 17:28 -0400, Adam Young wrote: I finally have enough understanding of what is going on with Tripleo to reasonably discuss how to implement solutions for some of the main security needs of a deployment. FreeIPA is an identity

Re: [openstack-dev] [TripleO] FreeIPA integration

On 04/06/2016 02:55 AM, Hayes, Graham wrote: On 06/04/16 03:09, Adam Young wrote: On 04/05/2016 08:02 AM, Hayes, Graham wrote: On 02/04/2016 22:33, Adam Young wrote: I finally have enough understanding of what is going on with Tripleo to reasonably discuss how to implement solutions for some

Re: [openstack-dev] [TripleO] FreeIPA integration

On 04/06/2016 10:38 AM, Hayes, Graham wrote: On 06/04/2016 17:17, Rich Megginson wrote: On 04/06/2016 02:55 AM, Hayes, Graham wrote: On 06/04/16 03:09, Adam Young wrote: On 04/05/2016 08:02 AM, Hayes, Graham wrote: On 02/04/2016 22:33, Adam Young wrote: I finally have enough understanding

Re: [openstack-dev] [puppet-keystone] Setting additional config options:

On 03/29/2016 04:19 PM, Adam Young wrote: Somewhere in here: http://git.openstack.org/cgit/openstack/puppet-keystone/tree/spec/classes/keystone_spec.rb spec is for the rspec unit testing. Do you mean http://git.openstack.org/cgit/openstack/puppet-keystone/tree/manifests/init.pp ? I

Re: [openstack-dev] [puppet] Propose Sofer Athlan-Guyot (chem) part of Puppet OpenStack core

+1 - good guy On 07/28/2016 09:58 AM, Ivan Berezovskiy wrote: +1, good job! 2016-07-28 18:50 GMT+03:00 Matt Fischer >: +1 from me! On Jul 28, 2016 9:20 AM, "Emilien Macchi" >

Re: [openstack-dev] [puppet] Proposing David Moreau Simard part of Puppet OpenStack CI core team

On 09/28/2016 10:06 AM, Emilien Macchi wrote: Until now, we had no specific team for dealing with Puppet OpenStack CI (aka openstack/puppet-openstack-integration project). But we have noticed that David was doing consistent work to contribute to Puppet OpenStack CI by adding more coverage, but

Re: [openstack-dev] [kolla-ansible] how do I unify log data format

On 07/14/2018 07:29 AM, Sergey Glazyrin wrote: Hello guys! We are migrating our product to kolla-ansible and as far as probably you know, it uses fluentd to control logs, etc. In non containerized openstack we use rsyslog to send data to logstash. Why not use rsyslog in containerized