[openstack-dev] [openstack-ansible] Blueprint discussion
"Testing: call tempest function from tox" https://blueprints.launchpad.net/openstack-ansible/+spec/testing-direct-tem pest I filed this blueprint for a potential enhance to our functional testing. Any thoughts OSA team? Michael Gugino On 9/29/16, 1:38 PM, "Davanum Srinivas" <dava...@gmail.com> wrote: >Hello everyone, > >The release candidate for OpenStack-Ansible for the end of the Newton >cycle is available! You can find the details at: > >https://releases.openstack.org/newton/index.html#newton-openstack-ansible > >Unless release-critical issues are found that warrant a release >candidate respin, this RC2 will be formally released as the final >Newton release on 6 October. You are therefore strongly encouraged to >test these! > >If you find an issue that could be considered release-critical, please >file it at: > >https://bugs.launchpad.net/openstack-ansible/+filebug > >and tag it *newton-rc-potential* to bring it to the OpenStack-Ansible >release crew's attention. > >Thanks, >Dims > >-- >Davanum Srinivas :: https://twitter.com/dims > >__ >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 This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. *** Walmart Confidential *** __ 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] [openstack-ansible] existing centralized syslog server
Hello Fabrice,
You should also set the rsyslog affinity to 0 for the infra_hosts. I’m not
sure if the affinity is necessary for the log hosts, but I don’t think it will
hurt. I recommend trying a few different ways and verify the corresponding
openstack_inventory.json file to ensure it meets your requirements.
Michael Gugino
Cloud Powered
(540) 846-0304 Mobile
Walmart ✻
Saving people money so they can live better.
From: fabrice grelaud
<fabrice.grel...@u-bordeaux.fr<mailto:fabrice.grel...@u-bordeaux.fr>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, July 6, 2016 at 12:15 PM
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [openstack-ansible] existing centralized syslog
server
Hi Michael,
Le 6 juil. 2016 à 17:07, Michael Gugino
<michael.gug...@walmart.com<mailto:michael.gug...@walmart.com>> a écrit :
Hello Fabrice,
I think the easiest way would be to set the affinity for each
controller/infrastructure host using 'rsyslog_container: 0' as seen in the
following section of the install guide:
http://docs.openstack.org/developer/openstack-ansible/install-guide-revised
-draft/configure-initial.html#affinity
ok, i look at this.
Actually (first deploy with a dedicated log server) , i have:
./scripts/inventory-manage.py -G
rsyslog_container | log1_rsyslog_container-81441bbb
So, from what you write, not to create a log_container on the log server, i can
modify my openstack_user_config.yml to be:
log_hosts:
log1:
affinity:
rsyslog_container: 0
ip: 172.29.236.240
Is that right ?
Next, you should add your actual logging hosts to your
openstack_user_config as seen here:
https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_de
ploy/openstack_user_config.yml.aio#L122-L124
Be sure to comment out the rsyslog-install.yml line of
setup-infrastructure.yml, and be sure that you make any necessary
modifications to the openstack-ansible-rsyslog_client role. Modifications
may not be necessary, depending on your needs, and you may be able to
specify certain variables in user_variables.yml to achieve the desired
results.
In openstack-ansible-rsyslog_client, the template 99-rsyslog.conf.j2 use :
*.* @{{ hostvars[server]['ansible_ssh_host'] }}:{{ rsyslog_client_udp_port
}};RFC3164fmt
I will test to ensure the IP is that from log1.
If yes, no more modification is needed.
Thanks again.
Regards
As always, make sure you test these modifications in a non-production
environment to ensure you achieve the desired results.
Michael Gugino
Cloud Powered
(540) 846-0304 Mobile
Walmart ✻
Saving people money so they can live better.
On 7/6/16, 10:24 AM, "fabrice grelaud"
<fabrice.grel...@u-bordeaux.fr<mailto:fabrice.grel...@u-bordeaux.fr>>
wrote:
Hi,
I would like to know what is the best approach to customize our
openstack-ansible deployment if we want to use our existing solution of
ELK and centralized rsyslog server.
We deploy openstack-ansible (mitaka 13.1.2 release) on our infrastructure
with for convenient and no risk a vm for syslog server role. That is ok.
But now if i want to use our centralized syslog server ?
What i need is to set ip address of our existing server to the rsyslog
client (containers + metal) and of course configure our rsyslog.conf to
manage openstack template.
So:
- no need to create on the log server a lxc container (setup-hosts.yml:
lxc-hosts-setup, lxc-containers-create)
- no need to install syslog server (setup-infrastructure.yml:
rsyslog-install.yml)
How can i modify my openstack-ansible environment (/etc/openstack_deploy,
env.d, conf.d, openstack_user_config.yml, user_variables.yml, playbook ?)
the most transparent manner and that permits minor release update simply ?
Thanks.
Fabrice Grelaud
Université de Bordeaux
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
This email and any files transmitted with it are confidential and intended
solely for the individual or entity to whom they are addressed. If you have
received this email in error destroy it immediately. *** Walmart Confidential
***
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listi
Re: [openstack-dev] [openstack-ansible] existing centralized syslog server
Hello Fabrice, I think the easiest way would be to set the affinity for each controller/infrastructure host using 'rsyslog_container: 0' as seen in the following section of the install guide: http://docs.openstack.org/developer/openstack-ansible/install-guide-revised -draft/configure-initial.html#affinity Next, you should add your actual logging hosts to your openstack_user_config as seen here: https://github.com/openstack/openstack-ansible/blob/master/etc/openstack_de ploy/openstack_user_config.yml.aio#L122-L124 Be sure to comment out the rsyslog-install.yml line of setup-infrastructure.yml, and be sure that you make any necessary modifications to the openstack-ansible-rsyslog_client role. Modifications may not be necessary, depending on your needs, and you may be able to specify certain variables in user_variables.yml to achieve the desired results. As always, make sure you test these modifications in a non-production environment to ensure you achieve the desired results. Michael Gugino Cloud Powered (540) 846-0304 Mobile Walmart ✻ Saving people money so they can live better. On 7/6/16, 10:24 AM, "fabrice grelaud" <fabrice.grel...@u-bordeaux.fr> wrote: >Hi, > >I would like to know what is the best approach to customize our >openstack-ansible deployment if we want to use our existing solution of >ELK and centralized rsyslog server. > >We deploy openstack-ansible (mitaka 13.1.2 release) on our infrastructure >with for convenient and no risk a vm for syslog server role. That is ok. >But now if i want to use our centralized syslog server ? > >What i need is to set ip address of our existing server to the rsyslog >client (containers + metal) and of course configure our rsyslog.conf to >manage openstack template. >So: >- no need to create on the log server a lxc container (setup-hosts.yml: >lxc-hosts-setup, lxc-containers-create) >- no need to install syslog server (setup-infrastructure.yml: >rsyslog-install.yml) > >How can i modify my openstack-ansible environment (/etc/openstack_deploy, >env.d, conf.d, openstack_user_config.yml, user_variables.yml, playbook ?) >the most transparent manner and that permits minor release update simply ? > >Thanks. > >Fabrice Grelaud >Université de Bordeaux > > > > >__ >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 This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. *** Walmart Confidential *** __ 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
