For many years Alcatel-Lucent’s documentation was all about authorized personnel only
. All of it. And not so long ago ALU opened a considerable part of its documentation portfolio to everyone
via its support portal
This portal internally is the same support portal available at alcatel-lucent.com domain though styles are now aligned with Nokia brand-kit. And being the same means that it is often slow in response, old-fashioned in UI and demands too much clicks and scrolling from you.
I hope that one day our documentation portal will be redesigned from ground up in a way that it would match current UX/UI patterns. In the meantime I took a humble attempt to make it a little bit more engineer-friendly.
That’s how I ended up with two projects:
- Web library with direct links to Nokia’ product documentation — NokDoc Lib
- And the CLI tool to fetch links to documentation and download it — NokDoc CLI Tool
Hypervisors diversity is definitely one of the benefits of having Nuage
managing your next-generation network. That means that we, as Nuage engineers, have to play with all kinds of hypervisors — like KVM, ESXi and Hyper-V to be more precise. As to me, I love to work with KVM most, simply because it gives you that feel that you are in control and can fine-tune or troubleshoot with granularity you want. Thanks to opensource tools like
and many many others!
But these tools won’t fit perfectly for every situation every time. For example consider a simple case of a Linux host with a bunch of VMs connected via Linux bridges and answer a simple question: how to determine what VM names correspond to what virtual network interfaces connected to what bridges? I have to say that this question arises quite often when you troubleshoot network connectivity between VMs or gathering network stats.
And the answer to this question can not be provided with above mentioned tools without some scripting. Indeed, in this post I will share a script called
brvirt which does the job by combining
[root@leo ~]# python brvirt.py
| Bridge | Interface | VM name | Domain ID | Int. MAC address |
| br0 | eno1 | | | 28:80:23:90:ea:28 |
| | vnet0 | cobbler | 8 | 52:54:00:5a:a9:2c |
| | vnet4 | nuage-dns | 4 | 52:54:00:db:45:92 |
| br1 | eno2 | | | 28:80:23:90:ea:29 |
| | vnet1 | cobbler | 8 | 52:54:00:9b:c2:dc |
| br999 | eno2.999@eno2 | | | 28:80:23:90:ea:29 |
Link: Github repo.
This DNS story started when I bought a domain with a specific need — to dynamically create and delete DNS records for Nuage Networks components we use during Proof Of Concepts and customers trials.
Earlier I used to rely on Dynamic DNS services (i.e. no-ip.com) whenever I needed a DNS name for my public endpoints. But this approach has two drawbacks:
- To use if for free you have to manually prolong you hostname once in a month. Drove me mad every time!
- In PoCs/trials you want your domain represent your product. Using
hostname.ddns.net in front of a customer is not something that speaks well for your product. And we all know that devil is in the details.
Therefore I decided to buy a domain that will represent a product we are offering and park it to some provider which offers robust, free and API-enabled DNS service. Google cloud DNS and DynDNS while being both cheap are not free. So I kept looking and ended up with Yandex DNS which has all three traits I was looking for. Lastly I automated this DNS workflow so everyone in my team could provision their own DNS entries via one shared tool.
You got it right, in this post I am going to tell you about a completely free DNS service from Yandex with a decent API you can use for your personal needs. And yes, this post is accompanied with a python script which leverages API and automates DNS records provisioning.
Recently I presented to you a project called PLAZA
which basically serves as a Web UI for python scripts. It was a pleasure to see that this project was welcomed well and some folks even asked how they can get PLAZA to play with. My fault, I wanted to release it so bad that I missed the part describing how to actually get it.
One way to get PLAZA that was available since the beginning – is cloning the github repo and building python virtual environment with all the packages. And I understand that nowadays this way seems too complicated and the case is ideal for learning some docker!
Join me in this journey for integrating a simple Flask application into a docker container.
I have updated this port with another write-up called Flask application in a production-ready container
Recently I revived my relationship with Python in an effort to beat routine tasks appearing here and there. So I started to write some pocket scripts
and, luckily, was not the only one on this battlefield – my colleagues also have a bunch of useful scripts. With all those pieces of code sent in email, cloned from repos, grabbed on network shares I started to wonder how much easier would it be if someone aggregated all of them, made a Web UI and shared this experience.
Thus, I started to build web front-end to python scripts with these goals in mind:
- allow people with zero python knowledge to use the scripts by interaction through simple Web UI;
- make script’s output more readable by leveraging modern CSS and HTML formatting;
- aggregate all the scripts in one repo but in a separate sandboxed directories to increase code manageability.
This short demo should give you some taste of what it is:
Disclaimer: I am nowhere near even a junior python or web developer. And what makes matters worse is that I used (a lot) very dangerous coding paradigm – SDD – Stackoverflow Driven Development. So, hurt me plenty if you see some awful mistakes.
Last week I faced a routine (and quite common) task to get the latest backups of current configuration and BOF files for ~700 routers on a customers network. Sure thing sane man would use some automatization techniques, which could be:
- 5620 SAM scripts
- some scripting language to grab latest backups from the global NE backup location on a SAM server
I tried it both ways and invite you under the cut to read about it.
Virtualenvwrapper’s windows port (
virtualenvwrapper-win) helps to manage your venvs on windows platform, yet it is not so straigtforward about using hooks like
postactivate. That is what official documentation has to say about this:
To run some commands after mkvirtualenv you can use hooks. First you need to define VIRTUALENVWRAPPER_HOOK_DIR variable. If it is set mkvirtualenv will run postmkvirtualenv.bat script from that directory. Version 1.2.0 (16-03-2015)
I tried to set
VIRTUALENVWRAPPER_HOOK_DIR and place
postactivate.bat there, but it didnt work out. The workaround I found for emulating
postactivate behaviour is to edit
postactivate.bat which is located in
It became quite a pain to get Web-based console working on ESXi hosts or vCenter servers with deprecation of NPAPI plugins in modern browsers. As for me, the most comfortable method to get a remote console access is to use standalone Virtual Machine Remote Console client (VMRC) which is available for free for major OSes. The sad part about VMRC is that you have to login to ESXi web client/vCenter, choose a desired VM and click on Launch VMRC link to get access. Too many unnecessary and annoying steps to take.
In my day to day work I have to deal with 2-4 VMs and what I want is to have their consoles 1-click away. In this post I’ll share a tiny Python script which composes links for VMs suitable for VMRC:
vmrc://firstname.lastname@example.org:443/?moid=vm-373 . Click on the previous link will trigger VMRC to connect to virtual console of a VM.