AWS using Ansible? Yes, it's possible!

-
  Although, I've used Ansible extensively for a lot of automation and orchestration tasks, using Ansible for AWS was indeed, a new territory for me.  This turned out to be a blessing, since along with using Ansible for AWS tasks, I also learnt how to use WSL (Windows Subsystem for Linux) on a Windows machine. Though WSL's been around for some time, I still hadn't come around to using it since I was mostly using my Macbook pro. Not anymore, though!  Anyway, I have listed below the steps to: Install WSL on Windows 11 23H2 patch Install AWS CLI on Ubuntu 22.04 (Exact version - 22.04.3 LTS) Install Ansible and the amazon.aws collection Use AWS CLI to get the list of  VPCs in the region - us-east-1 (or a region of your choice) Create a python file/script to get the list of VPCs in the region - us-east-1 (or a region of your choice) Create an Ansible playbook to get the list of VPCs in the region - us-east-1 (or a region of your choice.   You may download the complete installat
Post a Comment

Grafana and Oracle database - Part 2A - Installation of Influx DB

-

I am currently on InfluxDB v1.5, which you can download from here here.

Of course, I do understand that it isn't the latest version (current version, as on date, is 2.4). However, there are significant changes in InfluxDB v2.0 and above, which I haven't yet gotten around to implementing.

I prefer to download the tar.gz file and use the compiled executable as Oracle software owner (oracle) user - for obvious reasons, I don't want to perform yum/apt-get install (I don't want to do anything with root user 😊).

You may use wget to download the binaries to the desired location.

Refer the documentation for installation details.

NOTE: If possible, get a OS user - influxdb (or similar user) created. Else, use the Oracle software owner OS user (in my case - oracle).


$ whoami
oracle

$ mkdir -p /oracle/influxdb

$ cd /oracle/influxdb

$ wget https://dl.influxdata.com/influxdb/releases/influxdb-1.5.5_linux_amd64.tar.gz
--2022-09-19 05:17:29--  https://dl.influxdata.com/influxdb/releases/influxdb-1.5.5_linux_amd64.tar.gz
Resolving dl.influxdata.com (dl.influxdata.com)... 108.138.246.75, 108.138.246.34, 108.138.246.81, ...
Connecting to dl.influxdata.com (dl.influxdata.com)|108.138.246.75|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 22645770 (22M) [application/x-tar]
Saving to: ‘influxdb-1.5.5_linux_amd64.tar.gz’

100%[=================================================================================================================>] 22,645,770  17.4MB/s   in 1.2s   

2022-09-19 05:17:31 (17.4 MB/s) - ‘influxdb-1.5.5_linux_amd64.tar.gz’ saved [22645770/22645770]

$ ls -lrt

total 89944
-rw-r--r-- 1 oracle oinstall 92098809 Aug 18 12:49 influxdb-1.5.5_linux_amd64.tar.gz

 
Once the binaries are downloaded, tar and gunzip them under any preferred directory:

$ tar xzvf influxdb-1.5.5_linux_amd64.tar.gz
./influxdb-1.5.5-1/
./influxdb-1.5.5-1/etc/
./influxdb-1.5.5-1/etc/logrotate.d/
./influxdb-1.5.5-1/etc/logrotate.d/influxdb
./influxdb-1.5.5-1/etc/influxdb/
./influxdb-1.5.5-1/etc/influxdb/influxdb.conf
./influxdb-1.5.5-1/var/
./influxdb-1.5.5-1/var/lib/
./influxdb-1.5.5-1/var/lib/influxdb/
./influxdb-1.5.5-1/var/log/
./influxdb-1.5.5-1/var/log/influxdb/
./influxdb-1.5.5-1/usr/
./influxdb-1.5.5-1/usr/lib/
./influxdb-1.5.5-1/usr/lib/influxdb/
./influxdb-1.5.5-1/usr/lib/influxdb/scripts/
./influxdb-1.5.5-1/usr/lib/influxdb/scripts/influxdb.service
./influxdb-1.5.5-1/usr/lib/influxdb/scripts/init.sh
./influxdb-1.5.5-1/usr/share/
./influxdb-1.5.5-1/usr/share/man/
./influxdb-1.5.5-1/usr/share/man/man1/
./influxdb-1.5.5-1/usr/share/man/man1/influxd.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influxd-version.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influxd-config.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influxd-restore.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influxd-run.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influx.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influxd-backup.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influx_stress.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influx_inspect.1.gz
./influxdb-1.5.5-1/usr/share/man/man1/influx_tsm.1.gz
./influxdb-1.5.5-1/usr/bin/
./influxdb-1.5.5-1/usr/bin/influx_stress
./influxdb-1.5.5-1/usr/bin/influx_tsm
./influxdb-1.5.5-1/usr/bin/influx
./influxdb-1.5.5-1/usr/bin/influxd
./influxdb-1.5.5-1/usr/bin/influx_inspect
 

$ cd influxdb-1.5.5-1

$ ls -lrt
total 12
drwxr-xr-x 4 oracle oinstall 4096 Dec 19  2018 var
drwxr-xr-x 5 oracle oinstall 4096 Dec 19  2018 usr ==> All executables
drwxr-xr-x 4 oracle oinstall 4096 Dec 19  2018 etc ==> Config file

 

Three files of interest:

$ find . -name "influxd"
./usr/bin/influxd

$ find . -name "influx"
./usr/bin/influx

$ find . -name "influxdb.conf"
./etc/influxdb/influxdb.conf


Now, make sure that the first two executables are available in the PATH variable.

Make sure to modify .bash_profile of the Oracle software OS user as well.

$ export PATH=/oracle/influxdb/influxdb-1.5.5-1/usr/bin:$PATH

$ which influxd
/oracle/influxdb/influxdb-1.5.5-1/usr/bin/influxd

$ which influx
/oracle/influxdb/influxdb-1.5.5-1/usr/bin/influx

$ echo "export PATH=/oracle/influxdb/influxdb-1.5.5-1/usr/bin:\$PATH" >> ~/.bash_profile


Configure the below parameters in the conf file:

$ ls -ld /oracle/influxdb/influxdb-1.5.5-1/etc/influxdb/influxdb.conf

reporting-disabled = true

[meta]
  dir = "/oracle/influxdb/meta"
[data]
  dir = "/oracle/influxdb/data"
  wal-dir = "/oracle/influxdb/wal"
...

...
[http]
  enabled = true
  bind-address = ":8086"
  auth-enabled = true

Of course - dont' forget to create those directories:

$ mkdir -p /oracle/influxdb/meta /oracle/influxdb/data /oracle/influxdb/wal

 

Now, fire up influx DB as below:

$ nohup influxd -config /oracle/influxdb/influxdb-1.5.5-1/etc/influxdb/influxdb.conf >> /oracle/influxdb/influxdb-1.5.5-1/var/log/influxdb/influxd_$(hostname).log 2>&1 &

 

Verify that everything's fine in the logs:


Voila! Your influx DB instance is up and running.

A few things to note, especially for people from Oracle DB background:

1. Influx DB works similar to MySQL or Mongo DB - i.e., one instance --> many databases.

2. As I said before - two executables are important - influxd and influx (just like mysqld and mysql or mongod and mongo)

influxd - the Influx DB daemon 

influx - the command line utility to connect to the Influx DB - similar to SQL Plus

3. Influx DB is a time series DB. Hence, all data stored in the database is with the timestamp - the precision is configurable and can go up to nanoseconds.

4. Go through the documentation to learn more about influx CLI, creating DBs and the works.

 

Next up: Create your first Influx database, measurements, tags and fields - refer the primer here.

 

< Prev (Part 1: Introduction)                                                            Next (Part 2B: Influx DB data) >


Comments

Post a Comment

Popular posts from this blog

Solution to "End Program - WMS Idle"

-
Image
Though this topic is unrelated any Apps DBA topics, I found it necessary to share the solution so that everyone benifits out of it ! Issue: I used to receive the below error message whenever I tried to shutdown windows XP. A rather vexing problem, no doubt. Cause: This message appears because when windows is trying to shutdown and end all the running processes, the WMS idle process keeps working. Thus an end-program message appears. The two most common reasons for this are: Scout service run by Nero 7 Microsoft Office Communicator 2005 Solution: The fix is simple, disable the Nero 7 scout service if it is enabled. For this, go to Start > All Programs > Nero > Tools > Nero Scout . On this screen , Uncheck Enable the Nero scout. This will fix the issue for most of the users, for the rest of you who are not using Nero are most probably getting this error because of Microsoft Office Communicator 2005. For that you need to either manually exit the communicator 2005 from the s
Read more

Modify retention period of workflow queues

-
Yesterday, there was a requirement to increase the retention period of WF_DEFERRED and WF_BPEL_Q so that the developers could troubleshoot issues involving business events. This can be done this way: 1. Check the retention period of existing workqueues. SQL> SELECT owner, name, retention FROM all_queues WHERE name LIKE 'WF%'; OWNER           NAME                                                RETENTION --------------- --------------------------------------------- ------------------------------ APPS                 WF_BPEL_Q                                                0 APPLSYS         WF_INBOUND_QUEUE                             0 APPLSYS         WF_OUTBOUND_QUEUE                          0 APPLSYS         WF_SMTP_O_1_QUEUE                           0 APPLSYS         WF_DEFERRED_QUEUE_M                        0 APPLSYS         WF_DEFERRED                                            0 APPLSYS         WF_ERROR                                           0 AP
Read more

Check if UTL_FILE and FND_FILE are working fine

-
Yesterday, while troubleshooting a vexing ORA-29280 error, I came across 2 useful PL/SQL anonymous blocks that can be used to test FND_FILE and UTL_FILE to find out whether they are indeed working fine. UTL_FILE set serveroutput on DECLARE file_location VARCHAR2(256) := '<first entry on utl_file_dir>'; file_name VARCHAR2(256) := 'utlfile1.lst'; file_text VARCHAR2(256) := 'THIS IS A TEST'; file_id UTL_FILE.file_type; BEGIN file_id := UTL_FILE.fopen(file_Location, file_name, 'W'); UTL_FILE.put_line(file_id, file_text); UTL_FILE.fclose(file_id); EXCEPTION WHEN UTL_FILE.INVALID_PATH THEN dbms_output.put_line('Invalid path ' || SQLERRM); WHEN OTHERS THEN dbms_output.put_line('Others '|| SQLCODE || ' ' || SQLERRM); END; / References: Metalink (MOS) Note ID: 261693.1 FND_FILE set serveroutput on exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST'); HTH.
Read more