Skip to main content

Libvirt KVM fixed IP address


When playing with KVM LibVirt Vms, I often need them to have fixed IP address.
Ironically, I enjoy fixing them with DHCP.
Here is the “default” configuration I use in order to fix them.
Redefining the "default" network is done with:

virsh --connect qemu:///system net-destroy default
virsh --connect qemu:///system net-undefine default
virsh --connect qemu:///system net-define /tmp/network.xml
virsh --connect qemu:///system net-start default

Feel free to get inspiration:
<network>                                                   
  <name>default</name>                                      
  <uuid>7efbc96f-94e8-443f-820c-615d2e0331d5</uuid>         
  <forward mode='nat'/>                                     
  <bridge name='virbr0' stp='on' delay='0' />               
  <ip address='192.168.122.1' netmask='255.255.255.0'>      
    <dhcp>                                                  
      <range start='192.168.122.2' end='192.168.122.254' /> 
      <host mac="52:54:00:9a:81:00" name="centos6-00.vm.mihamina.netapsys.fr" ip="192.168.122.132" />
      <host mac="52:54:00:e0:0e:8a" name="centos6-01.vm.mihamina.netapsys.fr" ip="192.168.122.118" />
      <host mac="52:54:00:c1:ff:12" name="debian7-00.vm.mihamina.netapsys.fr" ip="192.168.122.144" />
      <host mac="52:54:00:06:a1:f4" name="debian7-01.vm.mihamina.netapsys.fr" ip="192.168.122.68" />
      <host mac="52:54:00:91:d1:96" name="debian7-02.vm.mihamina.netapsys.fr" ip="192.168.122.92" />
      <host mac="52:54:00:22:20:cd" name="fedora19-00.vm.mihamina.netapsys.fr" ip="192.168.122.20" />
      <host mac="52:54:00:1d:0f:9e" name="fedora19-01.vm.mihamina.netapsys.fr" ip="192.168.122.157" />
      <host mac="52:54:00:2a:a6:41" name="gitlab-c6-01.vm.mihamina.netapsys.fr" ip="192.168.122.235" />
      <host mac="52:54:00:f7:30:03" name="gitlab-c6-02.vm.mihamina.netapsys.fr" ip="192.168.122.54" />
      <host mac="52:54:00:86:a0:d6" name="win7-00.vm.mihamina.netapsys.fr" ip="192.168.122.152" />
      <host mac="52:54:00:e8:a8:b8" name="win7-01.vm.mihamina.netapsys.fr" ip="192.168.122.14" />
    </dhcp>                                                 
  </ip>                                                     
</network>                                                  


Comments

Popular posts from this blog

dockerfile multiline to file

Outputing a multiline string from Dockerfile
I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian.
But I also have a local mirror and would like to use it for packages installation.

Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file.

Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write.
Here you are:

RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl=ftp://packages-infra.mg.rktmb.org/pub/centos/7/base-reposync-7 " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 " >>…

npm run build base-href

Using NPM to specify base-href
When building an Angular application, people usually use "ng" and pass arguments to that invocation.
Typically, when wanting to hard code "base-href" in "index.html", one will issue:

ng build --base-href='https://ngx.rktmb.org/foo'


I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin.
I got the habit to build the application with "npm run build" before deploying it.

But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter.

npm run build --base-href='https://ngx.rktmb.org/foo


did not set the base href in indext.html

After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says:
You need to use −− to pass arguments to npm scripts. This did the job!
The command to issue is then:

npm run build -- --base-href='https://ngx.rktmb.org/foo'

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme.
I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create.
Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard:
"Create with shared configuration" will allow me to select the project I want the new one to share configuration with.

The new created project will use the same configuration as the project I selectThere will be no creation of Workflow and Issue Scheme that I need to cleanup

This fea…