After reading JFrogCLI-EnvironmentVariables
I would like to set JFROG_CLI_OFFER_CONFIG to false, but I have no idea.
I have tried jfrog config JFROG_CLI_OFFER_CONFIG=false, doesn't work.
if you're on Linux or macOS you can do
JFROG_CLI_OFFER_CONFIG=false jfrog rt ...
There is a sample here
The other option you have on Linux and macOS is
export JFROG_CLI_OFFER_CONFIG=false
jfrog rt ...
if you're on Windows you can do
set JFROG_CLI_OFFER_CONFIG=false
jfrog rt ...
Related
Trying to install openvpn3-client on my amazon Linux followed this documentation, facing below error
Packages skipped because of dependency problems:
openvpn3-13-0.beta1.el7.x86_64 from copr:copr.fedorainfracloud.org:dsommers:openvpn3
openvpn3-client-13-0.beta1.el7.x86_64 from copr:copr.fedorainfracloud.org:dsommers:openvpn3
openvpn3-selinux-13-0.beta1.el7.noarch from copr:copr.fedorainfracloud.org:dsommers:openvpn3
python36-dbus-1.2.4-4.el7.x86_64 from epel
python36-gobject-base-3.22.0-6.el7.x86_64 from epel
I have already installed epel following this
Amazon linux install openvpn3-client & dependencies as per
https://github.com/OpenVPN/openvpn3-linux
See the instructions on
https://community.openvpn.net/openvpn/wiki/OpenVPN3Linux how to
install pre-built OpenVPN 3 Linux packages on Debian, Ubuntu, Fedora,
Red Hat Enterprise Linux, CentOS and Scientific Linux.
1 solution was to switch from AWS Linux (lack of dependencies & updates) to Fedora on AWS. No longer have to build from source / add dependancices,
older versions had to add the repo as per the above.
When I did an upgrade to Fedora 36 the latest openvpn3-linux v18 client was built in. Did not have to manually upgrade / install it:
openvpn3-admin version --services
e.g: previous v17 suddenly stopped working spend 10 hours trying to debug
"Trying to install openvpn3-client" and reinstall:
openvpn3 config-import --config profile.udp.ovpn --persistent
openvpn3 config-manage --config profile.udp.ovpn --enable-legacy-algorithms true --show
openvpn3 session-start --config profile.udp.ovpn
openvpn3 sessions-list
openvpn3 session-manage --config profile.udp.ovpn --disconnect
Actually thinking it was a cipher AES-256-CBC legacy issue that others were having. It was not for some reason, permissions on install of the OpenVPN3 Linux client? as it was NOT creating a TUN.
So I made one myself (that was the actual issue) and it connected after asking for VPN Username & Password, no need to install again / reinstall afterall:
sudo ip tuntap add name tun0 mode tun
sudo ip link show
Other Amazon linux install openvpn3-client issues help is here: https://github.com/OpenVPN/openvpn3-linux/issues?q=cipher
How to get OpenStack version using Horizon or OpenStack client?
When I ran the command openstack --version, I got below output :
openstack 3.15.0
Now from this, how we can get which relesae of openstack it is e.g. newton, kilo?
Another question, if I have access to Horizon dashbord, is it possible to get the version of openstack from UI?
I think it's worth noting that openstack --version from the command line is only going to give you the version of the openstack client on the system you're looking at. openstack host list or nova service-list might give you a better idea of where openstack services are running in your openstack deployment.
I don't recall seeing a way to see specific OpenStack service versions through Horizon. From the command line on a given service's host (like nova, neutron, cinder, keystone), you should be able to list the packages as installed.
I think the canonical installation uses the distribution's package manager:
For yum-based systems like rhel and centos
sudo yum list installed | grep openstack
sudo yum list installed | grep nova
For aptitude-based systems
sudo dpkg -l | grep openstack
sudo dpkg -l | grep nova
From there, you'll have to cross reference the release with the version from the OpenStack documentation. Nova version 14 would be the Newton release, for instance. See the nova versions here. For the list of releases, look here.
nova-manage --version will give you the OpenStack version.
The output will be a number which corresponds to letter in the alphabet. For example
if output is 18 then its OpenStack ROCKY Version, since 18 corresponds to 18th letter in the alphabet.
17- Queen
18- Rocky
19- Stein
Each service which is installed in OpenStack is a package with a version. So usually we get versions of individual service. For example to find the nova version then,
nova --version
If you want to know all packages related to nova then,
pip list | grep nova
From above, you will get the nova client and nova versions then search for the versions in **https://releases.openstack.org/teams/nova.html. Here you will get the versions segregated with respect to OpenStack release names.
Get output from openstack --version command and compare against the following.
Rocky 3.16.0
Queens 3.14.0
Pike 3.12.0
Ocata 3.8.1
Newton 3.2.0
Mitaka 2.3.0
Liberty 1.7.3
Kilo 1.0.6
Juno 0.4.1
Icehouse 0.3.1
For future releases refer to:
https://docs.openstack.org/releasenotes/python-openstackclient/
It is always good to know which version of OpenStack environment you are working with. Before the Liberty
version, all projects except Swift had a version based on the year and month. Starting with Liberty, all
components have a traditional version structure X.Y.Z., where X is always the same in one release.
Here is an example for Mitaka:
keystone-manage --version
9.0.0
nova-manage --version
13.0.0
And here is an example of the old-fashioned version convention used in OpenStack Kilo:
keystone-manage --version
2015.1.0
nova-manage --version
2015.1.0
Also you can find the version on the System Information tab in the Admin menu at the right corner of
the page bottom. In Table 11-2 , several of the latest OpenStack releases are listed.
Table 11-2. OpenStack Releases
Series Releases Initial Release Date
Juno 2014.2 October 16, 2014
Kilo 2015.1 April 30, 2015
Liberty Nova 12.0; Keystone 8.0; Neutron 7.0; Swift 2.4 October 15, 2015
Mitaka Nova 13.0; Keystone 9.0; Neutron 8.0; Swift 2.6 April 7, 2016
Newton Nova 14.0; Keystone 10.0; Neutron 9.0; Swift 2.8 October 6, 2016 (planned)
From Openstack docs
In RHOSP you can simply check the file in controller
# cat /etc/rhosp-release
Red Hat OpenStack Platform release 13.0.10 (Queens)
This will give you the exact version of the openstack installed
The sad answer is: You can't.
At least this is true if you are just a user for an OpenStack setup and don't have access to the backplane, logging into the actual servers providing a service. The API is the only stable way to access the services. Each service may or may not have its own OpenStack version, they are not necessarily all the same.
In theory, looking up the service catalog should do the job you're asking for since it contains the endpoints for each service your OpenStack cloud provides. And part of the endpoint URLs is the endpoint version. Unfortunately that needs not necessarily match the module version of the service.
Looking up the catalog can be done like this:
openstack catalog list -c Endpoints -f json | jq '.[].Endpoints[]' | grep url| sort -u
(you get the idea). Maybe that includes the infromation you are looking for.
In case you don't have permissions (HTTP error 403) to run:
openstack service list
openstack host list
Then look for "id" version at OS_AUTH_URL address, found in your tenant RC file (you can download the RC file in Horizon, under Project > API Access).
For example, here I'm using curl and jq to filter id version from: https://my.openstack.redhat.com:13000/v3:
$ curl https://my.openstack.redhat.com:13000/v3 | jq '.[] | .id'
"v3.10"
# Or:
$ curl https://my.openstack.redhat.com:13000 | jq -r '.versions.values[] | .id'
v3.10
According to https://docs.openstack.org/api-ref/identity/v3/
My Openstack version is 3.10, which also known as "Queen" (or RHOSP 13).
nova-manage --version will give you the OpenStack version. The output will be a number which corresponds to letter in the alphabet. For example if output is 18 then its OpenStack ROCKY Version, since 18 corresponds to 18th letter in the alphabet.
How to install Airflow on Windows 7? getting below error while installing it using pip install apache-airflow :
---------------------------------------- Command "c:\users\shrgupta5\appdata\local\programs\python\python36-32\python.exe
-u -c "import setuptools, tokenize;__file__='C:\\Users\\SHRGUP~1\\AppData\\Loca l\\Temp\\pip-build-_yptw7sa\\psutil\\setup.py';f=getattr(tokenize, 'open', open) (__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __fi le__, 'exec'))" install
--record C:\Users\SHRGUP~1\AppData\Local\Temp\pip-_cwm0n u7-record\install-record.txt --single-version-externally-managed
--compile" fail ed with error code 1 in C:\Users\SHRGUP~1\AppData\Local\Temp\pip-build-_yptw7sa\ psutil\
I wouldn't bother trying to install Airflow on windows, even after you install it successfully you cannot run the airflow script due to a dependency on the unix-only module pwd
You can run Airflow on Windows by using the Docker setup from puckel https://github.com/puckel/docker-airflow.
Use VirtualBox and Docker Toolbox(legacy) and setup a docker-machine on your Windows computer (docker-machine create -d virtualbox --virtualbox-cpu-count "2" --virtualbox-memory "2048" default)
make sure to fork puckels git repo underneath c:/Users/yourusername/documents otherwise mounting of DAGS won't work
You should now be able to spin up Airflow e.g. by using the celery-executor setup with docker compose -f docker-compose-CeleryExecutor.yml up -d
I have setup a environment where I develop the DAGs on Windows, test them within the dockercontainer and then push the Dockerimage to Linux to production. I have added a more detailed tutorial here.
Airflow cannot be installed on Windows within the standard command prompt.
You need to use bash and afterwards change the config:
How to run Airflow on Windows
Download the source of airflow from pypi:
https://pypi.org/project/airflow/#files
Unzip and edit setup.cfg, then go to the install_requires section and change the version of psutil with the following: 'psutil>=5.4.7',
Finally, run python setup.py install in the source directory
user_1 (master *) 1_EchoServer $ python -m http.server 8000
Serving HTTP on 0.0.0.0 port 8000 (http://0.0.0.0:8000/) ...
127.0.0.1 - - [30/Sep/2017 18:57:11] "GET / HTTP/1.1" 200 -
Set up a simple server. I want to connect to it with ncat to learn HTTP.
I install ncat (pip install nmap):
user_1 Documents $ pip install nmap
Requirement already satisfied: nmap in c:\python36\lib\site-packages
Then, when I try and connect, cmd not found. It was working earlier. Not sure how I broke it.
user_1 Documents $ pip install nmap
Requirement already satisfied: nmap in c:\python36\lib\site-packages
user_1 Documents $ ncat -l 9999
bash: ncat: command not found
I am using git bash on windows, and I have set up python36 on c drive and changed env variables and path accordingly.
I have been in this problem today and I solved it.
the Nmap command must be in the $PATH environment variable for the discovery service account. To do this on windows do the following steps
Click Start > Control Panel > System
Click the Advanced tab, and select Environment Variables.
Edit the Path system variable and add the directory where Nmap is installed.
Restart the computer.
If you do this task, Nmap should be available to services on the computer and the command will be found in the terminal
The Python "nmap" package which you installed with pip install nmap is only an output parsing library. It does not include the Nmap binary. The "nmap" package available in the Windows Subsystem for Linux (a.k.a. Bash on Windows, a.k.a. Ubuntu on Windows) does not currently work properly and is unsupported.
The only place to get Nmap (and Ncat) in ready-to-use format (binary executable) on Windows is directly from nmap.org.
I have installed two version of postgreSQL on my Windows 7 dev box. Ver. 9.1 (32-bit) and 9.2 (64-bit). During installation I assigned ver. 9.1 port 5432 and ver 9.2 port 5433. However, whenever I run basic commands like createdb.exe from the 9.2\bin directory, the command runs against the wrong port. Regardless of what commands I run, they always default to the port of the first install (5432). The install directories and data directories are in different locations.
If you don't specify a port, the Postgres tools (e.g. psql) default to 5432. Use the -p switch to change the port that the tool should use, e.g.
psql -p 5433 mydb myuser
Or for the createdb command:
createdb -p 5433 the_new_db
Please read the respective chapters in the manual for details.
If you don't want to specify the port number each time, you can set an environment variable that is picked up by the Postgres tools. This is also explained in the manual: http://www.postgresql.org/docs/current/static/libpq-envars.html