1. This week I got a chance to attend Devconf India which held at Christ University Bangalore. As per stats, there were around ~1323 attendee and 110 speakers. There were around 14 parallel tracks (Agile, Blockchain, Cloud and Container, Community, Design, Developer Tools, DevOps, IOT, Machine Learning, Middleware, Platform, QE, Security, Storage) and BOFs, workshops so pretty much completely packed schedule.

    Day 1 started with a dance performance by university students and after that the keynote by Ric Wheeler about "Open source is better for companies/businesses, communities and developers" and he talked about back in the day how things used to happen and how far we have come now in terms of software businesses. He also talked about the why nowadays most of the organization are moving toward Open Source.

    After the keynote, I went to booth area where most of the communities booth were present (Fedora, Foreman, OpenShift, Sliverblue, Women who code, RDO, Mozilla, ElasticSearch, devopedia, Ansible) and spent some time answering some OpenShift related queries by participants.

    After the tea break, I went for my workshop, which was about “Getting start with OpenShift using MiniShift”. I shared the stage with Budhram and we had Anjan Nath, Jatan dedicated volunteer for this workshop (Thanks guys.). We got around 38 participants and everything went smoothly except some of the issues with the windows users due to expected reasons (no admin permission on system and C:\ drive was not used). We explained the basic navigation of OpenShift web UI, how to use Openshift client (oc) tool to connect to a cluster, how to deploy an application. We also covered some of the basic of kuberentes resources.

    After Lunch I spent most of the time roaming around the booth area, talking to different people. Met with a lot of old friends as usual.

    Day 1 end with the keynote by Karanbir Singh (kbsingh) about “Open Source won”, he talked about the phase when Indian Linux group was started and now it’s very hard to find any organization which is not consuming an opensource project.

    Some of us went outside for dinner and back early to hotel to get some rest  :)

    Day 2 started with the keynote by Christian Heimes about “Lessons about security”, he talked about a bit of Roman culture and how information saved in old days. He talked about recent hardware vulnerabilities and why you should always keep your software up to date especially the security fixes.

    After the tea break, I went to volunteer Baiju workshop, which was about “ RESTful API Development using Go”.  There were around 40 participants and most of them were familiar with the golang. Baiju started with a simple http server and then how you can build up your route on top of it without using any kind of framework to teach the logic what happens behind the scene. He then introduced a module `mux` which is used to filter out the request type (GET, DELETE, POST ...etc.) so that if a route only serves one request type then other should be ignored for it. He also talked about `negroni` for middleware use case.


     Then I attended a talk by Graham about “Data science in the cloud using Python”, he talked about how you can deploy Jupyter notebook on Openshift for personal use or even share it to other colleagues/friends in the organization.



    Day 2 ended with thank you note for all the organizers, volunteers, college faculty members, housekeeping staff and whoever involved making this conference success.


    Kudos to organizers and volunteers to pull off such an amazing conference.






    0

    Add a comment

  2. Landrush is pretty neat vagrant plugin if you need a DNS server which is visible to host and guest. For Mac OS it work out of the box but to make it work in Linux we have to make some configuration changes to dnsmasq.

    I assume that you are using latest vagrant and Virtualbox for this experiment. If you are using libvirt than please refer to Josef blogpost.

    Landrush DNS server runs on port 10053 (localhost) instead of 53 so we have to make entry to redirect requested domain name to our Landrush. Follow below steps and lets configure it.

    Install dnsmasq if not present
    $ sudo dnf install dnsmasq

    Add following to /etc/dnsmasq.conf
    listen-address=127.0.0.1

    Will create below file which redirect our .vm traffic to Landrush
    $ cat /etc/dnsmasq.d/vagrant-landrush
    server=/.vm/127.0.0.1#10053

    Will start/restart dnsmasq service and check status (should be active)
    $ sudo systemctl start dnsmasq.service
    $ sudo systemctl status dnsmasq.service
    ● dnsmasq.service - DNS caching server.
    Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; disabled; vendor preset: disabled)
    Active: active (running) since Thu 2015-12-24 11:57:47 IST; 2s ago
    Main PID: 19969 (dnsmasq)
    CGroup: /system.slice/dnsmasq.service
    └─19969 /usr/sbin/dnsmasq -k
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com systemd[1]: Started DNS caching server..
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com systemd[1]: Starting DNS caching server....
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: started, version 2.75 cachesize 150
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth DNSSEC ...ct inotify
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: using nameserver 127.0.0.1#10053 for domain vm
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: reading /etc/resolv.conf
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: using nameserver 127.0.0.1#10053 for domain vm
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: using nameserver 10.75.5.25#53
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: using nameserver 10.68.5.26#53
    Dec 24 11:57:47 dhcp193-61.pnq.redhat.com dnsmasq[19969]: read /etc/hosts - 2 addresses
    Hint: Some lines were ellipsized, use -l to show in full.


    Make sure you put '127.0.0.1' as nameserver to /etc/resolve.conf at first place.
    $ cat /etc/resolv.conf
    nameserver 127.0.0.1
    nameserver 8.8.8.8
    nameserver 4.4.4.4
    

    Make following change to your vagrant file
    $cat Vagrantfile
    PUBLIC_ADDRESS=10.1.2.2
    PUBLIC_HOST= "your_host.vm"
    config.vm.network "private_network", ip: "#{PUBLIC_ADDRESS}"
    config.vm.hostname = "#{PUBLIC_HOST}"
    config.landrush.enabled = true
    config.landrush.host_ip_address = "#{PUBLIC_ADDRESS}"
    config.landrush.tld = ".vm"
    confg.landrush.guest_redirect_dns = false

    $ vagrant landrush ls
    your_host.vm 10.1.2.2
    2.2.1.10.in-addr.arpa your_host.vm

    $ sudo netstat -ntpl
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 0.0.0.0:17500 0.0.0.0:* LISTEN 2946/dropbox
    tcp 0 0 10.65.193.61:44319 0.0.0.0:* LISTEN 14810/weechat-curse
    tcp 0 0 127.0.0.1:17600 0.0.0.0:* LISTEN 2946/dropbox
    tcp 0 0 127.0.0.1:45186 0.0.0.0:* LISTEN 433/GoogleTalkPlugi
    tcp 0 0 127.0.0.1:39715 0.0.0.0:* LISTEN 433/GoogleTalkPlugi
    tcp 0 0 127.0.0.1:17603 0.0.0.0:* LISTEN 2946/dropbox
    tcp 0 0 0.0.0.0:10053 0.0.0.0:* LISTEN 14966/ruby-mri
    tcp 0 0 127.0.0.1:2222 0.0.0.0:* LISTEN 15200/VBoxHeadless
    tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 16871/dnsmasq
    tcp 0 0 192.168.121.1:53 0.0.0.0:* LISTEN 16817/dnsmasq
    tcp 0 0 192.168.124.1:53 0.0.0.0:* LISTEN 16810/dnsmasq
    tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2647/cupsd
    tcp6 0 0 ::1:631 :::* LISTEN 2647/cupsd

    $ ping your_host.vm
    PING your_host.vm (10.1.2.2) 56(84) bytes of data.
    64 bytes from 10.1.2.2: icmp_seq=1 ttl=64 time=0.332 ms
    64 bytes from 10.1.2.2: icmp_seq=2 ttl=64 time=0.238 ms


    0

    Add a comment

  3. As you already know that OpenShift 3 offers a S2I (Source to Image) process to build applications where you can supply source code and choose a builder image. I was also trying to check it out and find out a way to configure route for deployed application.

    Development Setup
    ----------------------------
    - Fedora 22 server running on bare metal
    - Docker service should be running
    ** If you have already running service on your dev box which using port 7001 then stop those service (In my case, kubernetes/etcd service was  running and due to that openshift/origin container was not able to run)
      - Doc correction:  #1271468

    Setup
    --------
    1. Prerequisites - Since I am using openshift deployment using docker image so I didn't require to prerequisites setup but if you are interested then have a look to openshift doc.

     2. Start openshift within the container (Doc)

      $ sudo docker run -d --name "origin" \ 
          --privileged --net=host \ 
          -v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys:ro -v /var/lib/docker:/var/lib/docker:rw \ 
          -v /var/lib/openshift/openshift.local.volumes:/var/lib/openshift/openshift.local.volumes \ 
          openshift/origin start

    3.Deploy the registry
    $ docker exec -it origin /bin/bash
    # oadm registry --config=openshift.local.config/master/admin.kubeconfig \
                    --credentials=openshift.local.config/master/openshift-registry.kubeconfig
    deploymentconfigs/docker-registry
    services/docker-registry
    
    
    4. Install oc (openshift client) to remote host
    https://access.redhat.com/downloads/content/290/ver=3.0.0.0/rhel---7/3.0.2.0/x86_64/product-downloads
    
    
    5. Enable 8443 port from your dev box to use 'oc' from remote node.
    # firewall-cmd --add-port=8443/tcp --zone=public
    
    
    6. Connect to your dev box using 'oc'
    $ oc login
    Authentication required for https://:8443 (openshift)
    Username: test
    Password: ****
    Login successful.
    
    
    7. Create a project and app
    $ oc create test
    $ oc new-app openshift/deployment-example:v1
    
    
    8. Check project status
    $ oc describe service/deployment-example
    Name:   deployment-example
    Namespace:  test
    Labels:   app=deployment-example
    Selector:  app=deployment-example,deploymentconfig=deployment-example
    Type:   ClusterIP
    IP:   172.30.250.0
    Port:   8080-tcp 8080/TCP
    Endpoints:  172.17.0.4:8080
    Session Affinity: None 
    After all that done I was trying to configure route so I can able to access those deployed application outside of my dev box. I was reading openshift routing doc and trying to figure out what would can be used for it so I went with manual route setup which use 'openshift/origin-haproxy-router' image to create route but even after running that container on my dev box I was not able to get routing done, It would be great if someone help/point regarding it.

    Router Setup
    ------------
    Doc Used:https://github.com/openshift/origin/blob/master/docs/routing.md#manually
    $ docker run --rm -it -p 80:80 -p 443:443 openshift/origin-haproxy-router --master https://10.65.201.190:8443
    I1016 08:03:31.021472       1 router.go:122] Router is including routes in all namespaces
    Used ports on dev-box (if someone need to know)
    $ sudo netstat -ntpl
    Active Internet connections (only servers)
    Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
    tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      2130/openshift      
    tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      982/sshd            
    tcp        0      0 0.0.0.0:8443            0.0.0.0:*               LISTEN      2130/openshift      
    tcp6       0      0 :::80                   :::*                    LISTEN      6245/docker-proxy   
    tcp6       0      0 :::42706                :::*                    LISTEN      2130/openshift      
    tcp6       0      0 :::22                   :::*                    LISTEN      982/sshd            
    tcp6       0      0 :::46233                :::*                    LISTEN      2130/openshift      
    tcp6       0      0 :::7001                 :::*                    LISTEN      2130/openshift      
    tcp6       0      0 :::443                  :::*                    LISTEN      6237/docker-proxy   
    tcp6       0      0 :::4001                 :::*                    LISTEN      2130/openshift      
    tcp6       0      0 :::40418                :::*                    LISTEN      2130/openshift      
    tcp6       0      0 :::9090                 :::*                    LISTEN      1/systemd           
    tcp6       0      0 :::51716                :::*                    LISTEN      2130/openshift      
    tcp6       0      0 :::10250                :::*                    LISTEN      2130/openshift
    
    
    
    
    
    
    
    
     
     
    If you have some suggestion about routing then please let me know and I will update this post accordingly.
    5

    View comments

  4. Overview (Source)

    Docker needs storage to store containers and container images. The default storage option for Docker on Red Hat Enterprise Linux Atomic Host is an LVM thin pool while the default option on other variants of Red Hat Enterprise Linux is thin pool on loopback devices which is not recommended for production systems. The docker-storage-setup service can assist you in setting up an LVM thin pool. When docker starts, it automatically starts docker-storage-setup.
    By default, docker-storage-setup tries to find free space in the volume group backing the root volume and tries to setup a thin pool. If there is no free space in the volume group, docker-storage-setup will fail to set up an LVM thin pool and will fall back to using loopback devices.

    I was experimenting to make docker-storage-setup on a bare-metal because if you have single hard-drive on bare-metal and didn't have any free/unallocated space then docker-storage-setup service will always fail because it will not get required PE (Physical Extend)

    [root@dhcp201-188 ~]$ systemctl status docker-storage-setup.service -l
    ● docker-storage-setup.service - Docker Storage Setup
       Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled)
       Active: failed (Result: exit-code) since Wed 2015-10-07 02:45:23 EDT; 38s ago
      Process: 1418 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=5)
     Main PID: 1418 (code=exited, status=5)

    Oct 07 02:45:23 dhcp201-188.englab.pnq.redhat.com systemd[1]: Starting Docker Storage Setup...
    Oct 07 02:45:23 dhcp201-188.englab.pnq.redhat.com docker-storage-setup[1418]: Rounding up size to full physical extent 264.00 MiB
    Oct 07 02:45:23 dhcp201-188.englab.pnq.redhat.com docker-storage-setup[1418]: Volume group "fedora_dhcp201-188" has insufficient free space (1 extents): 66 required.
    Oct 07 02:45:23 dhcp201-188.englab.pnq.redhat.com systemd[1]: docker-storage-setup.service: main process exited, code=exited, status=5/
    NOTINSTALLED
    Oct 07 02:45:23 dhcp201-188.englab.pnq.redhat.com systemd[1]: Failed to start Docker Storage Setup.


    You can check available PE for any physical volume using 'pvdisplay'.

    [root@dhcp201-188 ~]$ pvdisplay  -m
      --- Physical volume ---
      PV Name               /dev/sda2
      VG Name               fedora_dhcp201-188
      PV Size               257.76 GiB / not usable 3.00 MiB
      Allocatable           yes
      PE Size               4.00 MiB
      Total PE              65985
      Free PE               1
      Allocated PE          65984

      PV UUID               kQX8gz-ePZe-njYM-b3mQ-owBh-ZZCT-7MBka6
      
      --- Physical Segments ---
      Physical extent 0 to 51199:
        Logical volume      /dev/fedora_dhcp201-188/root
        Logical extents     0 to 51199
      Physical extent 51200 to 63999:
        Logical volume      /dev/fedora_dhcp201-188/home
        Logical extents     0 to 12799
      Physical extent 64000 to 65983:
        Logical volume      /dev/fedora_dhcp201-188/swap
        Logical extents     0 to 1983
      Physical extent 65984 to 65984:
        FREE


    So I didn't have any free/unallocated space before and we can't create any if we have single hard drive which have boot mounted. I tried using Gparted live to resize my root mounted space but that didn't work out and I ended up reinstalling OS. This time I was much careful and around 200 GB saved for docker-storage-setup which is unallocated till now.

    After first boot to your system 'fdisk' will not list your unallocated/free space so I have to use 'parted' to find out details about partitions and  free space.

    #parted
    (parted) print free
    Model: ATA WDC WD5000AAKX-6 (scsi)
    Disk /dev/sda: 500GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags:

    Number  Start   End     Size    Type     File system  Flags
            32.3kB  1049kB  1016kB           Free Space
     1      1049kB  525MB   524MB   primary  ext4         boot
     2      525MB   277GB   277GB   primary               lvm
            277GB   500GB   223GB            Free Space


    Now I have to create a partition using free space so I can create a new volume group to use it with docker-storage-setup.

    (parted) mkpart primary ext4 283649 386049
    (parted) toggle 3 lvm                                                           
    (parted) print                                              
    Model: ATA WDC WD5000AAKX-6 (scsi)
    Disk /dev/sda: 500GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos
    Disk Flags:

    Number  Start   End    Size   Type     File system  Flags
     1      1049kB  525MB  524MB  primary  ext4         boot
     2      525MB   277GB  277GB  primary               lvm
     3      284GB   386GB  102GB  primary  ext4         lvm, lba


    We can now check with 'fdisk' utility about newly created partition detail also.

     [root@dhcp201-188 ~]$ fdisk  -l
    Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x9f119e31

    Device     Boot     Start       End   Sectors   Size Id Type
    /dev/sda1  *         2048   1026047   1024000   500M 83 Linux
    /dev/sda2         1026048 541581311 540555264 257.8G 8e Linux LVM
    /dev/sda3       554002432 754001919 199999488  95.4G 8e Linux LVM


    Now if you again check about physical volume and volume group you will find that we still don't have any volume group for '/dev/sda3'.

    [root@dhcp201-188 ~]$ pvdisplay -m
      --- Physical volume ---
      PV Name               /dev/sda2
      VG Name               fedora_dhcp201-188
      PV Size               257.76 GiB / not usable 3.00 MiB
      Allocatable           yes
      PE Size               4.00 MiB
      Total PE              65985
      Free PE               1
      Allocated PE          65984
      PV UUID               kQX8gz-ePZe-njYM-b3mQ-owBh-ZZCT-7MBka6
      
      --- Physical Segments ---
      Physical extent 0 to 51199:
        Logical volume      /dev/fedora_dhcp201-188/root
        Logical extents     0 to 51199
      Physical extent 51200 to 63999:
        Logical volume      /dev/fedora_dhcp201-188/home
        Logical extents     0 to 12799
      Physical extent 64000 to 65983:
        Logical volume      /dev/fedora_dhcp201-188/swap
        Logical extents     0 to 1983
      Physical extent 65984 to 65984:
        FREE
      
      "/dev/sda3" is a new physical volume of "95.37 GiB"
      --- NEW Physical volume ---
      PV Name               /dev/sda3
      VG Name              
      PV Size               95.37 GiB
      Allocatable           NO
      PE Size               0  
      Total PE              0
      Free PE               0
      Allocated PE          0
      PV UUID               Ryhj4d-x1al-ZDPn-WTcw-DWlg-8q8f-yrsAHA


    We have to create volume group so that it can be used with docker-storage-setup.

    root@dhcp201-188 ~]$ vgcreate docker_vol /dev/sda3
     [root@dhcp201-188 ~]$ pvdisplay
      --- Physical volume ---
      PV Name               /dev/sda2
      VG Name               fedora_dhcp201-188
      PV Size               257.76 GiB / not usable 3.00 MiB
      Allocatable           yes
      PE Size               4.00 MiB
      Total PE              65985
      Free PE               1
      Allocated PE          65984
      PV UUID               kQX8gz-ePZe-njYM-b3mQ-owBh-ZZCT-7MBka6
      
      --- Physical volume ---
      PV Name               /dev/sda3
      VG Name               docker_vol
      PV Size               95.37 GiB / not usable 4.00 MiB
      Allocatable           yes
      PE Size               4.00 MiB
      Total PE              24413
      Free PE               14608
      Allocated PE          9805
      PV UUID               Ryhj4d-x1al-ZDPn-WTcw-DWlg-8q8f-yrsAHA


    Now we have volume group which contain enough free PE for docker service uses, as per final step we have to put 'docker_vol' specification to '/etc/sysconfig/docker-storage-setup'

    [root@dhcp201-188 ~]$ cat /etc/sysconfig/docker-storage-setup      
    # Edit this file to override any configuration options specified in
    # /usr/lib/docker-storage-setup/docker-storage-setup.
    #
    # For more details refer to "man docker-storage-setup"
    VG=docker_vol


    Changing Docker Storage Configuration (source)

    If you change the storage configuration of Docker, you must also remember to remove the /var/lib/docker directory. This directory contains the metadata for old images, containers and volumes which are not valid for the new configuration. Examples of instances in which you might change the storage configuration include when you switch from using loop devices to LVM thin pool or if you switch from one thin pool to another. In the later case, you should also remove the old thin pool. 

    # systemctl stop docker
    # Remove old thin pool logical volume (lvremove docker/docker-pool)
    # rm -rf /var/lib/docker/
    # systemctl start docker




    Now you can check docker-storage-setup service and it no longer in failed state.

     [root@dhcp201-188 ~]$ systemctl start docker-storage-setup.service
    [root@dhcp201-188 ~]$ systemctl status docker-storage-setup.service -l
    ● docker-storage-setup.service - Docker Storage Setup
       Loaded: loaded (/usr/lib/systemd/system/docker-storage-setup.service; disabled; vendor preset: disabled)
       Active: inactive (dead) since Wed 2015-10-07 05:53:47 EDT; 1s ago
      Process: 27084 ExecStart=/usr/bin/docker-storage-setup (code=exited, status=0/SUCCESS)
     Main PID: 27084 (code=exited, status=0/SUCCESS)

    Oct 07 05:53:46 dhcp201-188.englab.pnq.redhat.com systemd[1]: Starting Docker Storage Setup...
    Oct 07 05:53:47 dhcp201-188.englab.pnq.redhat.com docker-storage-setup[27084]: Logical volume "docker-pool" changed.
    Oct 07 05:53:47 dhcp201-188.englab.pnq.redhat.com systemd[1]: Started Docker Storage Setup.


    Hope it will be helpful, happy hacking !!
    9

    View comments

  5. From yesterday I was trying to containerize ipython notebook so that I can deploy it anywhere without worrying about dependencies part using Fedora latest as base image for it . I was reading about how to make sure notebook can be run as daemon but didn't get any options which interested me so I went to old school way and used supervisor for handing this as a daemon which will also enable restarting ipython notebook in case there is any crash. This time I also thought not to by-pass any kind of SELinux flag when it's comes to sharing a different folder during spawning a container. 

    Dockerfile:

    FROM fedora:latest
    MAINTAINER Praveen Kumar "kumarpraveen.nitdgp@gmail.com"

    RUN dnf -y update
    RUN dnf -y install python-ipython python-virtualenv openssl supervisor

    RUN useradd -m ipython
    RUN mkdir -p /notebooks
    RUN chown -R ipython:ipython /notebooks

    VOLUME /notebooks
    WORKDIR /notebooks

    EXPOSE 7777

    ENV PEM_FILE /key.pem
    # $PASSWORD will get `unset` within notebook.sh, turned into an IPython style hash
    ENV PASSWORD Dont make this default
    ENV USE_HTTP 0

    ADD supervisord.conf /etc/supervisord.conf
    ADD notebook.sh /
    RUN chmod +x /notebook.sh

    USER ipython
    ENTRYPOINT ["/usr/bin/supervisord", "-l", "~/super.log", "-u", "ipython", "-n"]


    Git Hub Repo: https://github.com/praveenkumar/DockerFiles
    Docker Hub : https://hub.docker.com/r/kumarpraveen/fedora-ipython


    Any Suggestions/Comments? 
    0

    Add a comment

  6. Usually it's useful to disable touchpad while typing otherwise due to your palm, mouse cursor may go to different window/tab and select it (quite irritating right).

    last time I checked when using Fedora 17, there was an option "Disable touchpad while typing" and now in Fedora 22 this option is not there and I really need it, so I did some homework and found out that using 'synclient' tool I can enable those setting.

    Experiment with synclient:-

    # synclient -l
    Couldn't find synaptics properties. No synaptics driver loaded?

    # cp /usr/share/X11/xorg.conf.d/50-synaptics.conf /etc/X11/xorg.conf.d/50-synaptics.conf

    # cat /etc/X11/xorg.conf.d/50-synaptics.conf
    Section  "InputClass"
    Identifier  "touchpad catchall"
    Driver  "synaptics"
    MatchIsTouchpad  "on"

    ####################################
    ## The lines that you need to add ##
    # Enable left mouse button by tapping
    Option  "TapButton1"  "1"
    # Enable vertical scrolling
    Option  "VertEdgeScroll"  "1"
    # Enable right mouse button by tapping lower right corner
    Option "RBCornerButton" "3"
    ####################################

    MatchDevicePath  "/dev/input/event*"
    EndSection

    Logout and Login back

    # synclient -l
    Parameter Settings

    # syndaemon -i 1 -d

    (This will run syndaemon and disable touchpad while typing for 1 sec.)

    Check sysclient man page for other available options. If you know any better way then I would like to hear it.
     
    Source:
    * https://bbs.archlinux.org/viewtopic.php?id=152719
    * https://ask.fedoraproject.org/en/question/10975/where-are-the-touchpad-settings/

    2

    View comments

  7. I was preparing for one of CentOS meetup where I took systemd topic to talk about and since I am using systemd-nspawn in fedora from a long time and it really works as expected but there are some hacks which I had to do to make it work in CentOS.  This post is make a note of those hacks so in future I can refer it or if someone else facing same issue than it may help.

    Note: I am using CentOS cloud image on a openstack infrastructure. 

    1. You have to boot up system using audit=0 as kernel parameter.  Even systemd-nspwan will pop up this message when you are try to bootup/start a container. If you are not using '-j' option which attach logs to host journal then you container will boot up.

    2.  By default you will not have /var/log/journal directory because default journal configuration doesn't set to 'persistent' (check /etc/systemd/journald.conf) and make sure you update Storage config.

    3. Restart Journal ( $ sudo systemctl restart systemd-journald.service )

    4. Now create installroot for container using yum.
    $ sudo yum -y --nogpg --releasever=7 --installroot=/srv/mycontainer \
      install systemd passwd yum vim-minimal

    5. Start you container to change root password. (use 'passwd' command)
    $ sudo systemd-nspawn -D /srv/mycontainer

    6. Boot up your container with  Journald
    $ sudo systemd-nspawn -jbD /srv/mycontainer -M test

    7. Check your running container from host
    $ machinectl -a

    Happy Hacking ...!!
    2

    View comments

  8. Again a bit late from my side, apologizes for that. So we had our weekly planning meeting on 19 May at Red Hat Pune office. Event is approaching quite fast and we are making progress in term of planning. In this meeting we discussed about travel, schedule, outreach and swag.

    As usual we used http://piratepad.net/FUDConPunePlanning to keep notes and discussed different topic/blockers.

    Key-Points:-
    - List of speaker https://fedoraproject.org/wiki/FUDCon:Pune_2015#List_of_Speakers  along with preference.
    - In touch with Global Mobility for visa invitation letter.
    - First draft of schedule https://ethercalc.org/ut55d0qjcy
    - T-shirt design https://fedorahosted.org/design-team/ticket/376
    June first/second week for f22 release party + FUDCon advertisement.
    Discuss in Ambassadors meeting about Fedora 22 DVD's printing.
    - Site redesign complete and now in production.
    - Keep looking for different vendor to get swags.

    Note: If you are speaker then please blog about your presence and also we have nice buttons which you can add to your site. 
    0

    Add a comment



  9. This time I got chance to attend rootconf (Conference on infrastructure automation and DevOps) which held in Bangalore). Around 400 professional registered and attended it. At expo hall there were lot of different organizations who were promoting their cloud-infra solutions, tools developed for system administration and DevOps workflow.


    Day-1 started with conference introduction followed by 'Rewriting for scale' by Abhishek. I was quite surprise that his team rewrote complete code-base to Go language from ruby to achieve performance and to make it monotonous.

    Mike talked or rather I would say demoed about SaltStack which is again configuration Management tool, he presented basic concept about SaltStack to manage large number of servers/workstations and how effective it work. After tea break Anand talked about '10 reasons why should you should prefer PostgreSQL over MySQL'. he pointed out where MySQL failed and PostgreSQL outperformed.

    I went to expo hall and checked out solutions offering by different organizations to manage infrastructure. Most of folks were discussing about docker and how they are using is right now. After Lunch I put some Fedora Workstation DvD's (thanks to Ratandeep) to BrowserStack booth which was managed by Aditya. We also put upcoming FUDCon notice there. Some folks asked about what FUDCon is and how to register it.
    There were crisp talks about 'Inframer-Know your infra' by Saurabh who described about issue with distributed infrastructure and how inframer can help to manage it to a certain extent. Aditya talked about Project Atomic and why it needed, various component of it like OSTree, Cockpit and briefly explained about kubernetes.

    During Infrastructure BoF we discussed about docker and how it can be used, also why should we always inspect docker images instead of blindly pulling it and running it in production/staging. We also discussed about database rollbacks and how should we persist our data-store. We talked about docker usability is for application level, it not meant for storing data to containers because containers are non-persist.

    Day-2 started summary of day-1 followed by 'Why favor Icinga over Nagios' by Bernd. He talked about what Icinga provide in terms of scaling, configuration and integration side which is not easy with Nagios. He also talked about what new features Icinga web2 have and provided a brief demo about it. Shanker talked about using docker for microservices and how 'Rancher OS' make sense for docker. He gave a quick demo about build out microservices using rancher. After tea break I attended 'Managing distributed file systems' by Atin, he talked what challenge we face when manage different node in a distributed system and how can handle those using distributed consistent storage.

    After lunch Aditya talked about 'BrowserStack Security Breach, Lessons Learnt", his talk covered best practices to manage a large infra and do's and don'ts. During Lighting session I talked about Jenkins Job Builder and how we can manage job configuration with ymls and store it with SCM like we do with source code (Notes). I also announced upcoming FUDCon APAC event during Lighting talk. Razy talked about SELinux and why it's important.


    It was a great experience and I really liked BoF session where participants were discussing about real challenge they face and if someone have better solutions for it. Kudos to organizing team to manage each session on time.

    0

    Add a comment

  10. We had our scheduled FUDCon planning meeting yesterday at Red Hat office. Most of us were physically present and some of us joined over meeting-bridge.

    As usual we used http://piratepad.net/FUDConPunePlanning to keep notes and discussed different topic/blockers.

    Key-Points:-
    Entire minutes are appended below:

    28 April 2015

    Agenda + Minutes
    ---------------------------
     * Travel updates?
       * Next week (5th May) will start 3pm with Travel funding meeting (IRC)
       * Start planning for domestic travel
         * Mumbai to Pune
         * Pune Airport to Hotel
       * PJP and Niranjan to make a wiki page of speakers/travellers
         * https://fedoraproject.org/wiki/FUDCon:Pune_2015#List_of_Speakers
       * Meetings happening in #fudcon-planning every Friday at 1400 IST
         * Accepted several tickets
         * Deferred some; we'll keep going over the list.
         * All tickets https://fedorahosted.org/fudcon-planning/report/3
       * Prepare an invitation letter for them (for visa).
         * Huzaifa and PJP in touch with Global Mobility
       * Ask Ruth about us booking tickets instead of getting speakers/requestors to book tickets and reimburse after the conference
         * There is progress on this; Ruth has reimbursed a ticket already

     * Budget
       * (no update this week)
       * Make and maintain a publicly visible sheet to track expenses?
       * Need to keep tab on the number of accommodation requests
       * Sent a reminder to Ruth
         * Ruth replied; she's OK with using RH expense system


     * Scheduling
       * Niranjan and PJP doing this
         * Data needed from Siddhesh
           * How many rooms do we have? --> 3 for main tracks
           * https://ethercalc.org/ut55d0qjcy
       * (previous template of schedule at https://ethercalc.org/fudcon-schedule )
       * http://fudcon.in/program/sessions/accepted


     * Outreach
       * http://piratepad.net/marketing-plan-fudcon
       * A few slogans for posters are ready, feedback needed
         * More slogans welcome - please add to the etherpad.
       * There are some ideas for posters, discussion ongoing
       * Fedora badges - a few designs under consideration
       * http://piratepad.net/FudCon-outreach-list
         * this is for industry + mailing lists (communities)
         * we need help here with more lists + more volunteers to do the outreach.
       * http://piratepad.net/FUDCon-College-Outreach
         * Reach out to MIT to let them know about the event (mid/late May)
         * Do some sessions in colleges after exams over (exams get over mid-April)
         * Let's do in:
           * MIT-COE
           * Cummins
           * COEP
           * PCCOE
           * Sinhagad
         * 12 weekends before our event to do these sessions
       * Video series
         * Shreyank spoke with some video editors to get an idea of things to keep in mind; and also give them an idea of what we are looking for.
         * Response on fedora-india regarding guidelines.
         * Videos from FPL (Matthew Miller), jsmith, Kushal, Parag, Rahul, Joerg, etc. -- extolling the virtues of FUDCon + Pune
           * Kushal and Shreyank to work on this
           * Two videos:
             * One in April
             * One in May
           * Reach out to design/marketing team for editing help.


     * FUDCon.next planning
       * We should start a tradition to announce the next fudcon at the current one
       * Call for bids now open!  Will stay open till May 20:
         * https://lists.fedoraproject.org/pipermail/ambassadors/2015-April/023408.html

     * Website/Graphics
       * Reworked by Praveen and Siddhesh to include twitter feed, news feed, etc.
         * Working on it
       * Graphics status update?
         * Name tag sticker design (Reuse the Going to FUDCon graphic)
         * Brochure for speakers
         * T-shirt design
         * Going to FUDCon
           * https://jurankdankkal.fedorapeople.org/FUDCon/FUDConPune2015/final/goingto/goingto.png
           * https://jurankdankkal.fedorapeople.org/FUDCon/FUDConPune2015/final/flyer/flyer.svg
           * https://jurankdankkal.fedorapeople.org/FUDCon/FUDConPune2015/final/badges/badges.png
           * Please provide feedback on https://fedorahosted.org/design-team/ticket/359
           * 2011 designs
             * http://fudcon.in/2011/conference/promte-fudcon.html

     * FUDPub
       * Rupali reached out to Venue1
       * Potential Venue 1
         * Space for 100 people
         * Reasonable (approx 1800 per person)
         * RH has relationship; payments are easier
         * Close to cocoon
         * No limitation on sound limits - a nice party can be had.
       * Amit suggsts place where there is bowling option. 
         * Reached out to one place
           * Option 1: $5600 for unlimited games, food and drinks for unlimited people (max 250)
           * Option 2: $4800 for 150 people, limited to 12 lanes and unlimited food, drinks, games.
       * Blu-O: Bowling + Karaoke + Pool + Fuzzball
         * ₹220,000 for approx 140 people
         * includes unlimited games
         * includes unlimited food + drinks (aerated drinks included)
         * 7-11 pm. 
       * On paud road there is go-carting place, not sure if they have bowling too.
       * Rupali continuing to reach out to others
         * Another venue visit next week

     * Swag
       * Let's start thinking about this now; approach vendors.
       * Swag for Volunteers
         * tshirts (200) - (Pravin)
       * Swag for Organisers?
       * Swag for Speakers
         * Mugs (200)?
           * siddhesh's quote: 
           * shreyank's quote: 
         * Umbrellas (200) (for sweet Pune rains)
       * Swag in general <- div="" shreyank="">
         * buttons (3000)
         * tattoo pasties
         * stickers (5000) <- div="" siddhesh="">
         * pens (3000)
         * caps (300)
         * cloth bags (300)
         * diaries (200)  <- div="" siddhesh="">
         * bottles (200)
         * pen drives (200)
         * magic mint dispenser (200) <- amita="" div="">
         * socks (for bowling at FUDPub)
       * Fedora badge for attendees?(added to the FAS account)

     * Venue
       * WiFi
         * Siddhesh, Huzaifa, Rupali had a call with MIT sysadmin
         * MIT COE are keen on doing it; they need input from us.
           * Also talk about the Fedora mirror with them.
       * Power connector extensions
         * MIT are going to set this up.  Follow up
       * Note to speakers (include in prep email): In seminar hall: projectors are 4:3, screen quite small (don't include small text)
       * Refreshments for speakers lounge / otherwise

     * MIT meetups
       * What to do?
         * Packaging?
         * Bugzapping
       * Siddhesh to reach out to MCUG (this week, I promise!)

     * Volunteers
       * College reopens on Jun 15
       * Many students will be on leave till Jun 15
       * We should identify students who will be available in the break - e.g. students from Pune who don't plan to travel elsewhere; we don't need too much of their time anyway
         * Rupali to get a list of volunteers from MITCOE.

     * Mobile Application
       * No tweets from App itself
       * Starting with static schedule
       * No updates
       * Siddharth + Rohan had volunteered

     * Videographing
       * 4-5 Videographing camera's required
       * No updates
         * kpoint: Not an option. Rates too high (20k per day just for recording)
           * asked for clarification on rates; they might have subsidised options for us
         * hasgeek
           * They're  allowing us use of their equipment + train a few volunteers who can do  the recording.   Equipment needs to be brought from BLR to Pune.  Nice  gesture by them; but sounds complicated given the expensive equipment +  need to get volunteers to be trained.
         * Look for cheaper quotes from other professionals (Bipin)
         * Buy our own cameras? (Rupali)
         * Open source solutions for streaming (amit)
         * Last option will be to have a tiny webcam doing live Hangout -- advantage is it has auto-archival on Youtube.
           * amit: +1 for this option (or using the open source one for streaming)
    0

    Add a comment

Popular Posts
Popular Posts
Translate
Translate
Subscribe
Subscribe
Nice Links :-
Few clicks away
Blog Archive
Picture
Picture
Tags
Loading
Dynamic Views theme. Powered by Blogger.