[Openstack-operators] [openstack-ansible][queens] networking_sfc plugin not found - venv pb ?

OpenStack version : stable/queens OSA version : 17.0.9.dev22 python env version: python2.7 operating system : Ubuntu Server 16.04 Hi all, I was trying to install the *networking_sfc* plugin on my openstack environment thanks to OSA, but it failed. But I may have found the problem. I

Re: [Openstack-operators] [openstack-ansible] configuration file override

On 21.08.2018 12:32, jean-phili...@evrard.me wrote: My problem is that the servers that I'm using have their name defined as dcx-cy-blz (datacenter - chassis - blade). After installing openstack these names are reflected as the names of the hosts in nova. We would like to have our compute

Re: [Openstack-operators] [openstack-ansible] configuration file override

Hello Jean-Philippe, thank you for your answer. for the version I have this: root@ansible-ws1:~# openstack-ansible --version Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml " ansible-playbook 2.4.4.0 config file = /root/.ansible.cfg

[Openstack-operators] [openstack-ansible] configuration file override

Dear all, Openstack-ansible (OSA) allows us to override parameters in the configuration files as described here: https://docs.openstack.org/project-deploy-guide/openstack-ansible/draft/app-advanced-config-override.html there is the following statement: "You can also apply overrides on a

Re: [Openstack-operators] [openstack-ansible] How to manage system upgrades ?

Le lundi 30 juillet, Matt Riedemann écrivit : > On 7/27/2018 3:34 AM, Gilles Mocellin wrote: > > - for compute nodes : disable compute node and live-evacuate instances... > > To be clear, what do you mean exactly by "live-evacuate"? I assume you mean > live migration of all instances off each

[Openstack-operators] [openstack-ansible] galera issues with mitaka-eol

Hi All, In my continuing quest to install an OSA cluster with mitaka-eol in hopes of digging our to a non-eol release eventually I've hit another snag... setup-hosts plays out fine setup-infrastructure chodes soem where in galera-install the 1st galera container gets properly bootstrapped into

[Openstack-operators] Openstack Ansible ODL+OvS+SFC

Hi Openstack community ! I have a question regarding Openstack Ansible (OSA) and one deployement scenario "Scenario - OpenDaylight and Open vSwitch" (link below). https://docs.openstack.org/openstack-ansible-os_neutron/latest/app-opendaylight.html This is a lab test and I take inspiration

[Openstack-operators] [openstack-ansible] Change in our IRC channel

Hello everyone, Due to a continuously increasing spam [0] on our IRC channels, I have decided to make our channel (#openstack-ansible on freenode) only joinable by Freenode's nickserv registered users. I am sorry for the inconvenience, as it will now be harder to reach us (but it's not that

Re: [Openstack-operators] [openstack-ansible] How to manage system upgrades ?

Hi Matt, you are right. That's at least what I understand under 'live-evacuate'. The compute is still working, all VMs on it are running. Our VMs can all be live-migrated. We wrote a script to live-migrate all VMs to other computes, to do hardware maintenance on the evacuated compute server. I

Re: [Openstack-operators] [openstack-ansible] How to manage system upgrades ?

On 7/27/2018 3:34 AM, Gilles Mocellin wrote: - for compute nodes : disable compute node and live-evacuate instances... To be clear, what do you mean exactly by "live-evacuate"? I assume you mean live migration of all instances off each (disabled) compute node *before* you upgrade it. I

Re: [Openstack-operators] [openstack-ansible] How to manage system upgrades ?

Hi Gilles, sounds like a good idea. We've just written a script for live evacuate, which we can contribute after some refactoring. Gilles Mocellin schrieb am Fr., 27. Juli 2018 um 10:44 Uhr: > Hello ! > > Would be great to have a playbook to upgrade system parts of an > OpenStack Cloud ! >

[Openstack-operators] [openstack-ansible] How to manage system upgrades ?

Hello ! Would be great to have a playbook to upgrade system parts of an OpenStack Cloud ! With OpenStack Ansible : LXC containers and hosts. It would be awesome to do a controlled rolling reboot of hosts when needed... Different conditions to check : - for controllers : check galera

[Openstack-operators] [openstack-ansible] group_binds exceptions

Dear all, is there a way to define exceptions for the group_binds for a network definition? for instance we have something like this: - network: container_bridge: "vlan4" container_type: "veth" container_interface: "eth1" ip_from_q: "container" type:

Re: [Openstack-operators] [openstack-ansible] dropping selinux support

Also, this is the change that drops it, so feel free to vote with your opinion there too: https://review.openstack.org/578887 Drop SELinux support from os_swift On Thu, Jun 28, 2018 at 12:56 PM, Mohammed Naser wrote: > Hi everyone: > > This email is to ask if there is anyone out there opposed

[Openstack-operators] [openstack-ansible] dropping selinux support

Hi everyone: This email is to ask if there is anyone out there opposed to removing SELinux bits from OpenStack ansible, it's blocking some of the gates and the maintainers for them are no longer working on the project unfortunately. I'd like to propose removing any SELinux stuff from OSA based

[Openstack-operators] [openstack-ansible] Restarting our very own "SIG" teams

Hello, TL:DR; If you have spare cycles, join one of our interest groups! In the Queens cycle, I have formalised the "liaisons" work, making them an integral part of the Thursday's meeting agenda. Sadly, that initiative didn't work, as almost no liaison worked/reported on those meetings, and I

Re: [Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

> Right, you can set the stable-branch-type field to 'tagless' (see > http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n462) and > then set the branch location field to the SHA you want to use. Exactly what I thought. > If you would be ready to branch all of the roles at one

Re: [Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

Excerpts from Jean-Philippe Evrard's message of 2018-06-05 10:14:12 +0200: > Hello, > > *TL:DR;* If you are an openstack-ansible user, consuming our roles directly, > with tags, without using openstack-ansible plays or integrated repo, > then things will change for you. Start using git shas

[Openstack-operators] [openstack-ansible][releases][governance] Change in OSA roles tagging

Hello, *TL:DR;* If you are an openstack-ansible user, consuming our roles directly, with tags, without using openstack-ansible plays or integrated repo, then things will change for you. Start using git shas instead of tags. All other openstack-ansible users should not see a difference, even if

[Openstack-operators] [openstack-ansible] Sydney summit -- We'll be there!

Hello everyone, A small delegation of our openstack-ansible team will be in Sydney, and we are looking forward to meeting all of you! We'll have an ops feedback session during the forum happening on Monday 6th, 1:30 pm - 2:10 pm. If you're willing to get started with openstack-ansible,

[Openstack-operators] [openstack-ansible]: Ensure glance service fails while setting up Openstack

Hello, I am working on deploying a lab environment using openstack-ansible. While executing the setup-openstack.yml I encounter errors on the following task: TASK [os_glance : Ensure glance service] /etc/ansible/roles/os_glance/tasks/glance_service_setup.yml Looking into the output from

[Openstack-operators] Openstack-ansible and HAProxy

Dear all, Hope this is the right ML for this question, otherwise please let me know. I have setup an openstack-ansible based infrastructure (pike) with 3 controllers and 8 computes. Everything works fine except when i configure a dedicated IP to be shared between the ctrls. There are several

Re: [Openstack-operators] [openstack-ansible]: Container errors on task "lxc_container_create : Drop container network file (interfaces)"

On 13 October 2017 at 11:29, andres sanchez ramos wrote: > Hello guys, > > I am trying to deploy a lab Openstack environment using ansible in order to > get acquainted with this tool. Actually i am stuck with an error i am not > being able to resolve. It happens on

[Openstack-operators] [openstack-ansible]: Container errors on task "lxc_container_create : Drop container network file (interfaces)"

Hello guys, I am trying to deploy a lab Openstack environment using ansible in order to get acquainted with this tool. Actually i am stuck with an error i am not being able to resolve. It happens on the following task: TASK [lxc_container_create : Drop container network file (interfaces)]

[Openstack-operators] [openstack-ansible] Meetings change

Hello everyone, Some people on this planet are more aware of others of this fact: we have too many meetings in our life. I don't think OpenStack-Ansible should be so greedy to take 8 hours of your life a month for meetings. I therefore propose the reduction to 4 meetings/month: 3 bug triages and

[Openstack-operators] [openstack-ansible] restrictive umask / file permissions in target hosts

How do you deal with hosts which have a restrictive umask of 077 *before* openstack-ansible starts the setup? Do you start with the default umask of 022 and opt-in later to that security hardening[1]? What's the development policy of openstack-ansible regarding setting file or directory

Re: [Openstack-operators] Openstack-Ansible (Ocata branch) deployment failing - "No matching distribution found for mysql-python"

From: Andy McCrae <andy.mcc...@gmail.com> Date: Thursday, 4 May 2017 at 12:10 To: Eugene Duvenage <euge...@sahomeloans.com> Cc: "openstack-operators@lists.openstack.org" <openstack-operators@lists.openstack.org> Subject: Re: [Openstack-operators] Openstack-Ansible (Ocata

Re: [Openstack-operators] Openstack-Ansible (Ocata branch) deployment failing - "No matching distribution found for mysql-python"

Hi Eugene, You're right that error doesn't give us much. My best advice for a next step would be to manually run "bash /opt/op-venv-script.sh" from inside the repo container: dc2-controller-01_repo_container-7ce807b6. I've had similar issues, which is usually a constraints issue (we're working

Re: [Openstack-operators] Openstack-Ansible (Ocata branch) deployment failing - "No matching distribution found for mysql-python"

Hi Eugene, With just that error it's a bit difficult to see exactly why it's failing. Could you use paste.openstack.org (or similar) to paste a more detailed log of the error/output? I'd also suggest jumping into #openstack-ansible on the Freenode irc server, there are usually some people about

[Openstack-operators] OpenStack-Ansible Onboarding -day/time change

Just wanted to let everyone know the time and day for the OpenStack-Ansible Onboarding has changed. We will now have our onboarding on Wednesday, May 10 from 9:00 to 10:30. https://www.openstack.org/summit/boston-2017/summit- schedule/events/18711/ansible-project-onboarding Hope to see lots of

[Openstack-operators] [openstack-ansible] Way to cleanup existing Openstack-Ansible deployment

Hi All, I am trying to install Openstack Newton using OSA 14.0.8. Playbooks setup-hosts.yml and setup-infrastructure.yml are getting stuck at some point or other. Is there any way to cleanup everything which OSA has deployed. I want to re-run all the playbooks as if I am doing a fresh deployment.

Re: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

From: "Craft, Mike" <mike.cr...@viasat.com> Date: Thursday, March 2, 2017 at 7:50 PM To: "openstack-operators@lists.openstack.org" <openstack-operators@lists.openstack.org> Subject: [Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report cor

[Openstack-operators] (openstack-ansible) Mitaka 13.3.12 failing to report correct resource usage

Hello, Did an upgrade from liberty to mitaka and we are experiencing an issue where the audit of locally available compute resource usage is not seeing instances that were deployed prior to the upgrade. Has anyone experienced this before? We hard power cycled all the vms (and hypervisor) to

Re: [Openstack-operators] [openstack-ansible] Unbound problem

Hi Logan, Thanks for your quick answer and solution to the problem. I could do a complete reinstall on this system so I did that and tried again with your patch and it looks much better. Unbound is now deployed in containers only and the bare metal machines are configured to use those

Re: [Openstack-operators] [openstack-ansible] Unbound problem

Hi Andreas, Thanks for reporting this. I just pushed a patch to resolve this here https://review.openstack.org/#/c/431110/. If you are able to start with a fresh environment this should resolve the issue. The unbound service should only be installed in the containers, not the hosts, so that was

[Openstack-operators] [openstack-ansible] Unbound problem

Hi! I am using openstack-ansible 14.0.6-10 and have deployed Unbound but there seems to be a conflict with Dnsmasq (that is installed by OSA) and Unbound: Feb 8 19:20:21 Infra8 unbound[5637]: [1486578021] unbound[6973:0] error: can't bind socket: Address already in use for 0.0.0.0 Feb 8

Re: [Openstack-operators] [openstack-ansible] configuration to use nfs for glance and cinder

Hi Andy, Yes it probably does not matter if the variables are visible in other containers (you get a working system up and running anyway) but it is not the expected behavior when using limit_container_types. I did manage to get the variables limited to cinder_volume containers when I typed

Re: [Openstack-operators] [openstack-ansible] configuration to use nfs for glance and cinder

Hi Andreas, The way you're doing it at the end looks correct - the docs are not quite right on that one. The nfs_shares file will only get templated on the cinder_volumes hosts, as will the nfs_shares_config option - so in essence it shouldn't matter that the var isn't limited to volume hosts.

[Openstack-operators] [openstack-ansible] configuration to use nfs for glance and cinder

Hi! I need to ask how do you correctly configure nfs to be used with openstack-ansible newton (14.0.6). I think it is great that there is an production example file that uses nfs for glance and cinder (openstack_user_config.yml.prod.example) but the cinder config is not working for me. I

Re: [Openstack-operators] [openstack-ansible] Remove compute node command

On 2/1/2017 6:14 AM, Salman Toor wrote: hi, According to the Newton guide: http://docs.openstack.org/developer/openstack-ansible/newton/developer-docs/ops-remove-computehost.html The last command is # openstack-ansible remove_compute_node.yml -e node_to_be_removed=“compute1" With this I

Re: [Openstack-operators] [openstack-ansible] Remove compute node command

Hi again, Ok, next time i will file a bug report. With this thread I really want to thank OpenStack-Ansible team for their HEROIC efforts. I love this project: Simple, Cool and Effective :-) Best Regards.. Salman. PhD, Scientific Computing Researcher, IT Department, Uppsala University. Senior

Re: [Openstack-operators] [openstack-ansible] Remove compute node command

On Wed, Feb 1, 2017 at 4:16 PM, Andy McCrae wrote: > Hi Salman, > > Thanks for pointing that out - I'll file a fix for that now ( > https://review.openstack.org/427950 ) > > If you find any more it'd be great if you could file a bug in launchpad: >

Re: [Openstack-operators] [openstack-ansible] Remove compute node command

Hi Salman, Thanks for pointing that out - I'll file a fix for that now ( https://review.openstack.org/427950 ) If you find any more it'd be great if you could file a bug in launchpad: https://bugs.launchpad.net/openstack-ansible We triage bugs once a week (on Tuesdays), so we usually pick them

Re: [Openstack-operators] [openstack-operators][openstack-ansible] Optioanal services documentation for Newton

Hi, Thanks Melvin! I already been to these links and I don’t think these links contains the information about optional services. For example FWaaS, LBaaS or even Ceilometer. Those are what I am looking for the Newton release. Mitaka version works fine but just want to check if there is any

Re: [Openstack-operators] [openstack-operators][openstack-ansible] Optioanal services documentation for Newton

Hey Salman, Maybe this will help - http://docs.openstack.org/project-deploy-guide/openstack-ansible/newton/ - the documentation has changed a bit since Newton ( http://docs.openstack.org/developer/openstack-ansible/newton/ ) On Sun, Jan 22, 2017 at 2:12 PM, Salman Toor

[Openstack-operators] [openstack-operators][openstack-ansible] Optioanal services documentation for Newton

Hi, Wondering can someone help me pointing the openstack-ansible (Newton) guide for optional services? I have found for Mitaka but not for Newton. Basically looking for a similar link for Newton (Following is for Mitaka):

Re: [Openstack-operators] [openstack-operators][openstack-ansible]

Hi JP, Firstly thank you for your response. Over the weekend, I did something kind of similar to what you describe. 1. Built a AIO (inside main OSA) @ 16.04/Newton 2. took it's venv files and placed them in the higher level OSAs repo but as - Example: glance-xenial.tgz 3. copied the

Re: [Openstack-operators] [openstack-operators][openstack-ansible]

Hello, This sounds like an interesting issue that we should fix as soon as possible. May I ask you more details on the channel? It’s still brainstorming, but I think that if you clear facts, destroy/upgrade one controller node, then make sure this controller node has a repo under 16.04, it

[Openstack-operators] [openstack-operators][openstack-ansible]

Hi All, I am trying to upgrade a multinode cluster that has been very valuable in our environment. The idea was to start at trusty/mitaka and get to xenial/newton. Step1 mitaka -> newton on a trusty environment went fine. Step2 trusty to xenial is not going well and I could use some help. So

Re: [Openstack-operators] [openstack-ansible] networking services of compute nodes on LXC

*To: *"openstack-operators@lists.openstack.org" < > openstack-operators@lists.openstack.org> > *Subject: *[Openstack-operators] [openstack-ansible] networking services > of compute nodes on LXC > > > > Hello, > > I need to install the networking services of the comp

[Openstack-operators] [openstack-ansible] networking services of compute nodes on LXC

Hello, I need to install the networking services of the compute nodes into LXC, just like networking services on the infra nodes (neutron_agents_container) so that i can leverage eth11 and eth12 interfaces within the container on the compute nodes for my setup (DVR). How openstack-ansible should

Re: [Openstack-operators] [openstack-ansible] OVS+VLAN Networks Scenario

Hi Sławek Kapłoński, Thank you for your response. 1. In br-provider bridge I don't see any interface through which packets should be send. Is this bridge used as "external bridge"? Yes, it is used as "External Bridge". i added the interface eth12 within the *node01_neutron_agents container* to

[Openstack-operators] [openstack-ansible] OVS+VLAN Networks Scenario

Hi All, Context: openstack-ansible tag: 14.0.1 ML2 plug-in: OpenvSwitch Project / External networks: VLAN OS: Ubuntu 16.0.4 I would like to implement OVS with VLANs following these 2 docs [1][2] but things didn't work for me. I cannot ping my provider network:

[Openstack-operators] [openstack-ansible] tenant VLAN overlays

Hi, I am looking at openstack-ansible and would like to deploy using tenant VLAN overlays rather than VXLAN I have read here however that the VXLAN bridge is mandatory http://docs.openstack.org/developer/openstack-ansible/liberty/install-guide/overview-hostnetworking.html >> OpenStack

Re: [Openstack-operators] openstack-ansible - recovery of failed infrastructure host

Thanks for the suggestions. We’ll run the openstack-ansible scripts on a new infrastructure host. -- ben > On 24 Oct 2016, at 6:40 PM, Melvin Hillsman wrote: > > Hey Ben, > > Unfortunately I do not have way to confirm with you right now but also > suggest you

Re: [Openstack-operators] openstack-ansible - recovery of failed infrastructure host

Hey Ben, Unfortunately I do not have way to confirm with you right now but also suggest you create a backup of your database as a matter of caution and general best practice. If you can backup anything else that would be a good thing to consider as well. Kind regards, -- Melvin Hillsman Ops

Re: [Openstack-operators] openstack-ansible - recovery of failed infrastructure host

Hi Ben, If you stand up a new infrastructure host with the same IP address and name in openstack_user_config then execute the setup-hosts, setup-infrastructure and setup-openstack plays it should put everything back in place for you without further intervention. Jesse IRC: odyssey4me On

[Openstack-operators] [OpenStack-Ansible] Mitaka Upgrade

Hi All, If this is RTFM please point me there and I apologize. If not: We are testing the Liberty to Mitaka transition with OSAD. Could someone please advise if these were the correct general steps. osad multinode (VMs/instances inside a osad cloud) built with latest 12.X liberty osad 1. save

Re: [Openstack-operators] [OpenStack-Ansible] Liberty to Mitaka upgrade?

On 20 April 2016 at 04:27, Dale Baley wrote: > Is there a document or guide for upgrading from Liberty to Mitaka yet? > Hi Dale, The active work to test and implement any plays to assist with upgrades has not yet been implemented for Liberty->Mitaka. We hope to do this

[Openstack-operators] [OpenStack-Ansible] Liberty to Mitaka upgrade?

Is there a document or guide for upgrading from Liberty to Mitaka yet? thanks, dale ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [OpenStack-Ansible] Liberty and Ubuntu 16.04

Hi I am wondering if there will be possible to run Ubuntu 16.04 LTS with Liberty and the openstack-ansible project? Are you planning to "support" that? Regards, Andreas Vallin ___ OpenStack-operators mailing list

Re: [Openstack-operators] [Openstack-Ansible] Example of Ceph with Cinder using OpenStack-Ansible

Thanks for your quick response Trueman, will give a try very soon. /Salman ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Openstack-Ansible] Example of Ceph with Cinder using OpenStack-Ansible

quot; <openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>> Cc: Andreas Vallin <andreas.wal...@uppmax.uu.se<mailto:andreas.wal...@uppmax.uu.se>> Subject: [Openstack-operators] [Openstack-Ansible] Example of Ceph with Cinder using

[Openstack-operators] [Openstack-Ansible] Example of Ceph with Cinder using OpenStack-Ansible

Hi, Recently we have get started with OpenStack-Ansible. So far things looks good but now we want to use Ceph backend for cinder. Can someone show a reference configuration of how to get started? Thanks in advance. Regards.. Salman. PhD, Scientific Computing Researcher, IT Department,

Re: [Openstack-operators] [openstack-ansible] centos support

On 02/18/2016 01:01 PM, Abel Lopez wrote: We talked a bit about making OSAD 'EL' compatible, but we ultimately decided against it. There were various architectural differences that made it not worth the effort. I don't know if anyone else was seriously considering the work. Would highly

Re: [Openstack-operators] [openstack-ansible] centos support

We talked a bit about making OSAD 'EL' compatible, but we ultimately decided against it. There were various architectural differences that made it not worth the effort. I don't know if anyone else was seriously considering the work. > On Feb 18, 2016, at 9:41 AM, Wade Holler

Re: [Openstack-operators] [openstack-ansible]

On 02/17/2016 02:00 PM, Wade Holler wrote: > Well it almost does. Except on my neutron agents container I ended up with a > eth12 > > And I do have a flat network plumbed in to the infrastructure host ( on which > the neutron agent container resides ) via br-vlan. > > Thoughts? > > Thank

Re: [Openstack-operators] [openstack-ansible]

Hi Major, Well it almost does. Except on my neutron agents container I ended up with a eth12 And I do have a flat network plumbed in to the infrastructure host ( on which the neutron agent container resides ) via br-vlan. Thoughts? Thank you for the engagement and previous prompt rely! I

Re: [Openstack-operators] [openstack-ansible]

On 02/17/2016 01:23 PM, Wade Holler wrote: > Going to ask this question without much data or background as I hope someone > very familiar with openstack-ansible will be able to easily answer it. > > I tried to follow the install guide and network config pretty closely. > > All is well except

[Openstack-operators] [openstack-ansible]

Hi All, Going to ask this question without much data or background as I hope someone very familiar with openstack-ansible will be able to easily answer it. I tried to follow the install guide and network config pretty closely. All is well except my physical compute nodes don't have an eth12.

Re: [Openstack-operators] [openstack-ansible] Mid Cycle Sprint

Hi everyone, Thank you all for responding and giving your feedback. Given that the Ops Mid Cycle [1] is in the UK (15-16 Feb) and AnsibleFest [2] is also in the UK (18 Feb), and also that everyone seems ok with the UK as a location for the mid cycle then we shall have it in the UK! The Ops Mid

[Openstack-operators] [openstack-ansible] Mid Cycle Sprint

Hi everyone, At the Mitaka design summit in Tokyo we had some corridor discussions about doing a mid-cycle meetup for the purpose of continuing some design discussions and doing some specific sprint work. *** I'd like indications of who would like to attend and what

Re: [Openstack-operators] openstack-ansible virt_type=lxc

Hello, On 11/18/2015 08:02 PM, Wade Holler wrote: > Just a little help needed. > on trusty > > > using openstack-ansible ( allinone ) > changed user_variables nova_virt_type to lxc > re-run os-nova-install > > Something else I need to do? > I've not played with the LXC hypervisor type in a

[Openstack-operators] [openstack-ansible] Documentation update planning

Hi everyone, In the community meeting [1] this week we'll be having a facilitated discussion with regards to documentation improvements for OpenStack-Ansible. If you have any feedback you'd like considered, would like to be part of the conversation, or are keen to contribute then please add to

[Openstack-operators] [openstack-ansible] Fedora/CentOS/other Support

Hi everyone, There has been interest expressed from various corners to support more than just Ubuntu in OpenStack-Ansible. While the project is very happy to work on this, no-one has yet stepped up to take a lead role in the execution of this work. The current community has done some research

[Openstack-operators] openstack-ansible virt_type=lxc

Just a little help needed. on trusty using openstack-ansible ( allinone ) changed user_variables nova_virt_type to lxc re-run os-nova-install Something else I need to do? When launching an instance I get the no hosts found. And in nova-conductor log I get the CPU model error 2015-11-18

[Openstack-operators] [openstack-ansible] Mitaka Summit Summary

Hi everyone, I've put together some thoughts based on the Mitaka Summit from the OpenStack-Ansible point of view: http://odyssey4me.github.io/openstack/ansible/mitaka/summit/2015/11/17/mitaka-summit.html Please feel free to ping me with any feedback! Thanks, -- Jesse Pretorius IRC: odyssey4me

[Openstack-operators] [openstack-ansible] Mitaka Summit Schedule

Hi everyone, I've added the final details for the summit sessions to the etherpad: https://etherpad.openstack.org/p/openstack-ansible-mitaka-summit Our sessions are open to anyone with an interest in deploying OpenStack with Ansible. Note that our two primary topics for discussion are:

[Openstack-operators] [openstack-ansible] Mitaka Summit sessions

Hi everyone, As the Mitaka summit draws nearer, I'd like a broad view of what people would like to discuss at the summit. This can include anyone's input! Obviously our space and time will be limited, so any sessions that we don't get to formally do at the summit we'll either try to do informally

[Openstack-operators] [openstack-ansible] Release: Kilo 11.1.0

Hi everyone, The openstack-ansible community is pleased to announce our release of the Kilo 11.1.0 milestone. This release fixes 57 bugs and implements 4 major blueprints, including: * Keystone as a Federated Identity Provider * Keystone as a Federated Service Provider * Horizon Federation