default deployment tools rhel satelite and ubuntu landscape

By OK -


    Satellite 6.2 introduces remote execution, automating workflows and enabling users to take multiple actions against groups of systems, such as rebooting a system after a patch install or conduct rolling upgrades across hundreds of systems as easily as one. Users can easily build a script library, share scripts and share repeatable workflows, enabling less experienced administrators to execute complex workflows. In addition, users can schedule tasks and use new dashboards for enhanced interaction with systems under management.

    Deploying a single server

    Just install the Landscape Quickstart package:
    sudo add-apt-repository ppa:landscape/16.06
sudo apt-get update
sudo apt-get install landscape-server-quickstart
    After it finishes, access it with a browser like https://hostname.example.com/
    Where hostname.example.com is the output of hostname -f on that machine, or just hostname if that fails to resolve.

    Deploying for Scale Out

    If you have Juju, you can deploy Landscape in a scalable manner by following these steps:
    sudo add-apt-repository ppa:juju/stable
sudo apt-get update
sudo apt-get install juju-quickstart
juju-quickstart --no-browser bundle:~landscape/landscape-dense-maas/landscape-dense-maas
    Then get the IP of the haproxy/0 unit and access that with your browser:
    juju status haproxy/0

    Using Landscape

    You should then see the web UI after filling in your name and contact details

    Comments

    Post a Comment

    Popular posts from this blog

    HAproxy logging

    By OK -
    ubuntu@ubuntu:/etc/haproxy$ cat /etc/rsyslog.d/haproxy.conf # Create an additional socket in haproxy's chroot in order to allow logging via # /dev/log to chroot'ed HAProxy processes $ModLoad imudp $UDPServerRun 514 local0.* -/var/log/haproxy-0.log local1.* -/var/log/haproxy-1.log ### keep logs in localhost ## $AddUnixListenSocket /var/lib/haproxy/dev/log ------------------- ubuntu@ubuntu:/etc/haproxy$ cat /etc/haproxy/haproxy.cfg global chroot /var/lib/haproxy user haproxy group haproxy log 127.0.0.1   local0         log 127.0.0.1   local1 notice daemon frontend www     bind 192.168.40.128:8282    # haproxy public IP     default_backend as-backend    # backend used backend as-backend    balance leastconn    mode http  server as1 192.168.40.128:8082 check    # application srv 1 defaults log ...
    Read more

    teamcity Automatic Agent Start under Linux

    By OK -
    Automatic Agent Start under Linux To run agent automatically on the machine boot under Linux, configure daemon process with the  agent.sh start  command to start it and  agent.sh stop  command to stop it. Refer to an example procedure below: 1. Navigate to the services start/stop services scripts directory: cd /etc/init.d/ 2. Open the build agent service script: sudo vim buildAgent 3. Paste the following into the file : #!/bin/sh ### BEGIN INIT INFO # Provides: TeamCity Build Agent # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start build agent daemon at boot time # Description: Enable service provided by daemon. ### END INIT INFO #Provide the correct user name: USER="agentuser" case "$1" in start) su - $USER -c "cd BuildAgent/bin ; ./agent.sh start" ;; stop) su - $USER -c "cd BuildAgent/bin ; ./agent....
    Read more

    NFS mount add in fstab _netdev instead of default | firewall-cmd --list-all

    By OK -
    Redhat recommends us to add  _netdev  option for NFS file system in /etc/fstab. So that they can be mounted after starting the networking service. Alternative ways to refer to partitions: Label : LABEL=label Network ID Samba : //server/share NFS : server:/share SSHFS : sshfs#user@server:/share Device : /dev/sdxy (not recommended) Example #1 //192.168.1.134/share_name /mnt/share_name cifs username=server_user,password=server_password,_netdev 0 0 ^ Path to your share ^ Mountpoint ^ Username ^ Password ^ See note A Note A: The  _netdev  options makes sure the mount is only attempted AFTER a network connection has been established. Example #2 10.10.10.1:/vol1/fs1 /data nfs defaults,_netdev 0 0 ============================ [root@localhost ~]# firewall-cmd --list-all public   target: default   icmp-block-inversion: no   interfaces:   sources:   services: dhcpv6-client high-availabi...
    Read more