Re: [openstack-dev] [openstack-ansible] existing centralized syslog server

[fabrice grelaud]

> Le 7 juil. 2016 à 15:02, Jesse Pretorius  a 
> écrit :
> 
> On 7/6/16, 3:24 PM, "fabrice grelaud"  wrote:
> 
>> 
>> 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)
> 
> To add more rsyslog targets for logs you can see in 
> https://github.com/openstack/openstack-ansible-rsyslog_client/blob/stable/mitaka/defaults/main.yml#L56-L73
>  that there is an example of the changes you need to make to 
> /etc/openstack_deploy/user_variables.yml to include additional targets.

Really great… ;-)

> 
> You may be able to do away with the log host altogether as you desire by 
> simply leaving the ‘log_hosts’ group out of the 
> /etc/openstack_deploy/openstack_user_config.yml and 
> /etc/openstack_deploy/conf.d/*.yml files. This is an untested code path so 
> you may find that we make assumptions about the presence of the log_host so 
> please register bugs for any issues you find so that we can eradicate those 
> assumptions. To my mind the log host is not required for a deployment if the 
> deployer so chooses (and especially if the deployer has alternative syslog 
> targets in-place).

No issues found.
I launched the playbook setup-hosts.yml, everything good.
I tested to launch the rsyslog-install.yml playbook and i got "skipping: no 
hosts matched" as expected.

Yours assumptions look good. 

And an « openstack-ansible setup-everything.yml » with the tag « rsyslog_client 
» did the rest...  

> 
>> 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 ?
> 
> As long as you’re only editing things in user space (i.e. In 
> /etc/openstack_deploy/) and not in-tree (i.e. In /opt/openstack-ansible/) 
> then the minor upgrade process is documented here: 
> http://docs.openstack.org/developer/openstack-ansible/mitaka/install-guide/app-minorupgrade.html
> 
> I hope that this answers your questions!
> 

Perfect ! Thanks a lot…

> 
> Rackspace Limited is a company registered in England & Wales (company 
> registered number 03897010) whose registered office is at 5 Millington Road, 
> Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be 
> viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may 
> contain confidential or privileged information intended for the recipient. 
> Any dissemination, distribution or copying of the enclosed material is 
> prohibited. If you receive this transmission in error, please notify us 
> immediately by e-mail at ab...@rackspace.com and delete the original message. 
> Your cooperation is appreciated.
> __
> 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


__
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

[Jesse Pretorius]

On 7/6/16, 3:24 PM, "fabrice grelaud"  wrote:

>
>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)

To add more rsyslog targets for logs you can see in 
https://github.com/openstack/openstack-ansible-rsyslog_client/blob/stable/mitaka/defaults/main.yml#L56-L73
 that there is an example of the changes you need to make to 
/etc/openstack_deploy/user_variables.yml to include additional targets.

You may be able to do away with the log host altogether as you desire by simply 
leaving the ‘log_hosts’ group out of the 
/etc/openstack_deploy/openstack_user_config.yml and 
/etc/openstack_deploy/conf.d/*.yml files. This is an untested code path so you 
may find that we make assumptions about the presence of the log_host so please 
register bugs for any issues you find so that we can eradicate those 
assumptions. To my mind the log host is not required for a deployment if the 
deployer so chooses (and especially if the deployer has alternative syslog 
targets in-place).

>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 ?

As long as you’re only editing things in user space (i.e. In 
/etc/openstack_deploy/) and not in-tree (i.e. In /opt/openstack-ansible/) then 
the minor upgrade process is documented here: 
http://docs.openstack.org/developer/openstack-ansible/mitaka/install-guide/app-minorupgrade.html

I hope that this answers your questions!


Rackspace Limited is a company registered in England & Wales (company 
registered number 03897010) whose registered office is at 5 Millington Road, 
Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be 
viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may 
contain confidential or privileged information intended for the recipient. Any 
dissemination, distribution or copying of the enclosed material is prohibited. 
If you receive this transmission in error, please notify us immediately by 
e-mail at ab...@rackspace.com and delete the original message. Your cooperation 
is appreciated.
__
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

[Michael Gugino]

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 
mailto:fabrice.grel...@u-bordeaux.fr>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, July 6, 2016 at 12:15 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
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 
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" 
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/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

Re: [openstack-dev] [openstack-ansible] existing centralized syslog server

[fabrice grelaud]

Hi Michael,

> Le 6 juil. 2016 à 17:07, Michael Gugino  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" 
> 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

__
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

[Michael Gugino]

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" 
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

[openstack-dev] [openstack-ansible] existing centralized syslog server

[fabrice grelaud]

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