Installing a VM Fedora 23 Cloud Atomic with KVM – Part 1

Step 1 :

Download Fedora Cloud Atomic

Step 2:

Creates files to use in generation of init.iso
user-data , here you can configure your ssh keys and password for the user fedora
Download user-data
meta-data, here you can configure instance-id name and fqdn of vm
Download meta-data
init.iso will be used in order to use in boot process to configure the mentioned data
If you want to generate the init.iso just run this command:

~/l/r/v/cloud.init genisoimage -output cloudinit.iso -volid cidata -joliet  -rock user-data meta-data 
I: -input-charset not specified, using utf-8 (detected in locale settings)
Total translation table size: 0
Total rockridge attributes bytes: 331
Total directory bytes: 0
Path table size(bytes): 10
Max brk space used 0
183 extents written (0 MB)

Steps to create the vm:

Selección_101 Selección_100 Selección_099 Selección_098 Selección_097 Selección_096 Selección_095 Selección_094 Selección_093 Selección_092 Selección_091

Steps to Connect:

Then connect to the server with the correct ip address , user fedora and the correct password typed in user-data. If you use my init.iso, the password is atomicfedora.

Step to detect network interface:

Now, you need to change the ip address from dhcp to fixed, please edit the name of your interface.

[fedora@fedora ~]$ pwd
[fedora@fedora ~]$ hostname -f
[fedora@fedora ~]$ ip a s |grep -v lo | egrep -i "^2:*"|awk  '{print $2}'|sed 's/://'
[fedora@fedora ~]$ 


Step to configure fixed network:

Fill some values with your correct ip range

[fedora@fedora network-scripts]$ cat ifcfg-ens3 
# Generated by dracut initrd
[fedora@fedora network-scripts]$ 

Then down an up interface:

[fedora@fedora network-scripts]$ sudo su -
-bash-4.3# ifdown ens3 && ifup ens3
Device 'ens3' successfully disconnected.
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/1)

Then try to do network testing, ping, dns, etc..


Step to check Atomic:

-bash-4.3# atomic host status
  TIMESTAMP (UTC)         VERSION    ID             OSNAME            REFSPEC                                                
* 2016-04-19 19:04:34     23.106     05052ae3bb     fedora-atomic     fedora-atomic:fedora-atomic/f23/x86_64/docker-host     

Get some info about the next container to install and info of our docker configuration.

-bash-4.3# atomic info fedora/cockpitws
INSTALL: /usr/bin/docker run -ti --rm --privileged -v /:/host IMAGE /container/atomic-install
UNINSTALL: /usr/bin/docker run -ti --rm --privileged -v /:/host IMAGE /cockpit/atomic-uninstall
RUN: /usr/bin/docker run -d --privileged --pid=host -v /:/host IMAGE /container/atomic-run --local-ssh
-bash-4.3# docker info
Containers: 0
Images: 0
Server Version: 1.9.1
Storage Driver: devicemapper
 Pool Name: atomicos-docker--pool
 Pool Blocksize: 524.3 kB
 Base Device Size: 107.4 GB
 Backing Filesystem: xfs
 Data file: 
 Metadata file: 
 Data Space Used: 62.39 MB
 Data Space Total: 2.147 GB
 Data Space Available: 2.085 GB
 Metadata Space Used: 40.96 kB
 Metadata Space Total: 8.389 MB
 Metadata Space Available: 8.348 MB
 Udev Sync Supported: true
 Deferred Removal Enabled: true
 Deferred Deletion Enabled: true
 Deferred Deleted Device Count: 0
 Library Version: 1.02.109 (2015-09-22)
Execution Driver: native-0.2
Logging Driver: journald
Kernel Version: 4.4.6-301.fc23.x86_64
Operating System: Fedora 23 (Twenty Three)
CPUs: 1
Total Memory: 993.1 MiB

Run atomic host upgrade, in order to upgrade the system.

-bash-4.3# atomic  host upgrade
Updating from: fedora-atomic:fedora-atomic/f23/x86_64/docker-host

Receiving metadata objects: 


Next part will show you how to configure docker storage backend and install cockpit container as a service.



Reference 1

Reference 2

Leave a Reply