What is World IPv6 Launch?

Organized by the Internet Society, World IPv6 Launch on 6 June 2012 is intended to motivate organizations across the industry – including Internet service providers (ISPs), hardware makers, and web companies – to prepare for and permanently enable Internet Protocol version 6 (IPv6) on their products and services as Internet Protocol version 4 (IPv4) address space runs out.

This web site has been accessible via IPv6 since last year thanks to burst.net link to Hurricane Electric. And now I have configured CloudFlare to serve the content of the site via their CDN network which is also IPv6-enabled.

For home IPv6 connectivity I am using Ukrainian NetAssist tunnel broker which has delegated me a /48 block. I am actually using IPv6 in my LAN for all communications with occasional fallback to IPv6 for some services that does not support it yet.

So I am prepared for World IPv6 Launch.

Frankly speaking, I will celebrate the World IPv6 Launch day when I notice the first SSH brute force attack on my servers using IPv6 link.

Yandex-Import-Id: 61907928.366051546.1337588139.6716b286801600fc9c318745a3c0d97c

Having played a lot with HP Cloud and Canonical OpenStack installation, I decided to install OpenStack on my own home server. In order to gain better understanding about all the processes involved I decided not to use devstack script and follow the installation guides with the packages already available in Ubuntu Server 12.04 LTS (Precise Pangolin).

Surprisingly, setting up Keystone, Nova Compute, and Glance went really well with almost no effort from my side and I was even able to launch an instance of Ubuntu Server 12.04 running in nested KVM, which in turn was running on Compute virtual instance in KVM. So I had 2 levels of virtualization and it was still working quite well.

Then I decided to make Swift (Object Store) authenticating against Keystone (instead of built-in swauth). And this took a bit longer than expected.

Для работы мне требуется несколько вещей, в этом посте я опишу интернет провайдера, банк и оборудование, которыми я пользуюсь.

libvirt is a technology by RedHat that implements a single interface for different types of virtualization methods. Personally I am using it for kvm/qemu and LXC but the list on their website is much larger and includes UML, Xen, OpenVZ and even VMWare ESX and GSX hypervisors.

Browsing for various OpenStack docks had eventually brought me to an extremely nice howto on scsi-target-utils on fedoraproject.org.

A while ago I was searching for the docs on how to actually become an iSCSI target but the one I found - using iscsi on ubuntu 10.04 required to use a kernel module and I had some weird problems (too weird to start diagnosing just for fun).

So if you combine the target (server) setup from the fedoraproect.org with initiator (client) from the howtoforge, you will get a pretty decent iSCSI playground.

In ubuntu the package required for target is tgt.

In order for the server-side settings to be preserved across reboots, the configuration must be stored via tgt-admin utility (notice that this is a frontend to tgtadm):

1

tgt-admin -dump > /etc/tgt/conf.d/my-target.conf

Місяць тому я подав документи у Міжрегіональний центр видачі паспортів, а вчора отримав новий паспорт.

Знову їздив двічі, цього разу через те, що пропустив наступний пункт у правилах:

Після закінчення відповідного терміну для отримання паспорта громадянина України для виїзду за кордон необхідно з внутрішнім паспортом та (за наявності) діючого закордонного підійти до робочих місць 8,9.

Дата видачі у самому паспорті - 10 квітня, тобто документ був готовий через 16 робочих днів.

Видача паспортів працює протягом усього робочого дня центру і займає 5 хвилин, але зранку люди створюють чергу на отримання паспортів ще до відкриття центру.

If you have not extensively used Ubuntu One earlier and migrated to Ubuntu Precise (12.04), you may see the following IPCError when open Ubuntu One Control Panel:

The reason for this is 927572 in the old Control Panel code, in Ubuntu Precise this switch was removed. However some users might have already disabled their synchronization service.

To re-enable this, open ~/.config/ubuntuone/syncdaemon.conf in your favorite editor (don’t use sudo) find the following text:

1

files_sync_enabled = False

Please change the value to True so it reads

1

files_sync_enabled = True

Save the file and re-open the control panel. Syncdaemon should now start and control panel will work.

1.0.3 is mostly a bugfix release.

• Properly format estimation time (982221)
• Order the Recently Published Files list by mtime (981726)
• Use ubuntuone-client icons if icon-theme is not ubuntu-mono (981350)
• Remove old ubuntuone-indicator.desktop file (982118)
• Refresh quota after uploads, downloads and unlinks (982164)
• Automatically restart after upgrade (983361)

Subsequent upgrades won’t require the users to relogin as indicator will restart itself automatically after every upgrade.

Further announcements will be posted at Announcements page only.

If you add ppa:rye/ubuntuone-extras, you’ll get all the updates automatically:

1
2
3

sudo apt-add-repository ppa:rye/ubuntuone-extras
sudo apt-get update
sudo apt-get install indicator-ubuntuone

About two years ago I published the post on Ubuntu One Indicator, which at that time simply displayed the current synchronization state right from syncdaemon by listening to DBus signals. Then it started to grow, attempting to estimate the time needed for Ubuntu One to complete the operations.

Basically it looked like this:

Earlier this week I decided that I need to get some real-world experience with Vala and since I have found the python-based indicator to consume about 40Mb of residential memory I decided to rewrite the indicator completely.

A couple of days and bug reports later…

Well, not much different, added some menu entries, but let’s add the file.

Yes, finally, it calculates the current transfer rate and provides the ETA for the whole queue to be completed. It takes into account only Upload and Download processes. Since Ubuntu One has greately improved the metadata processing speed, metadata operations can be almost neglected.

However at the moment Downloads are not estimated properly since SyncDaemon does not provide size info on Downloads, bugreport pending.

The 1.0.0 version is available in ppa:rye/ubuntuone-extras, for precise the package was renamed to indicator-ubuntuone to be in line with other packages. Installing transitional ubuntuone-indicator package will install indicator-ubuntuone, so don’t be alarmed.

The project page was renamed to indicator-ubuntuone too, “one-indicator” was a weird name, really.

The new indicator installs an autostart file to /etc/xdg/autostart so it should not be launched automatically. Old per-user autostart file can be safely removed, by default it is at ~/.config/autostart/ubuntuone-indicator.desktop). For those who are interested, the compiled binary is located at /usr/lib/indicator-ubuntuone/indicator-ubuntuone.

This is a call for testing. The upcoming 1.0.2 version contains the estimation process described above and if you have some spare time please help me testing it.

Grab a package below according to your architecture and install it using the Software Center.

• i386 indicator-ubuntuone
• amd64 indicator-ubuntuone

These all come from my daily PPA which gets automatically built by Launchpad using the recipe.

Please report the bugs you may find via Launchpad bug tracker and if you’d like to help translating it to your native language, head over to Launchpad translations.

Upstart is an event-based replacement for the /sbin/init daemon which handles
starting of tasks and services during boot, stopping them during shutdown and
supervising them while the system is running.

Upstart scripts have always seemed to be weird to me, somebody who learned about SysV init subsystem in Mandrake and Slackware long time ago. It seemed like Upstart was lacking lot of features but it turns out I just needed to understand what I was looking for.

So, when I found a need of a startup script, I decided to stop treating upstart as magic and here are my Upstart examples.

• Respawning a dead daemon.
• Monitoring the respawn limit.
• Disable an Upstart task.
• Listing, starting, stopping and restarting Upstart jobs.