Hi Michael,
> Le 6 juil. 2016 à 17:07, Michael Gugino <[email protected]> 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" <[email protected]>
> 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: [email protected]?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: [email protected]?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
