The OpenWRT is modified based on KVM OpenWRT 15.05.1 to suitable for OpenStack Tacker.
The procedure is following as below:
wget https://archive.openwrt.org/chaos_calmer/15.05.1/x86/kvm_guest/openwrt-15.05.1-x86-kvm_guest-combined-ext4.img.gz \
mkdir -p imgroot
sudo kpartx -av openwrt-x86-kvm_guest-combined-ext4.img
# Replace the loopXp2 with the result of above command, e.g., loop0p2
sudo mount -o loop /dev/mapper/loopXp2 imgroot
sudo chroot imgroot /bin/ash
# Set password of this image to blank, type follow command and then enter two times
# Set DHCP for the network of OpenWRT so that the VNF can be ping
uci set network.lan.proto=dhcp; uci commit
sudo umount imgroot
sudo kpartx -dv openwrt-x86-kvm_guest-combined-ext4.img
1. Stop tacker service
sudo systemctl stop devstack@tacker
2. In the PyCharm, open the tacker (/opt/stack/tacker) and debug with:
/usr/local/bin/tacker-server --config-file /etc/tacker/tacker.conf
Abstract: Network Functions Virtualization (NFV) has emerged as a networking technology from telecom industry to provide agility and flexibility in the deployment of network services and to reduce the Capital Expenditures (CAPEX) and the Operating Expenses (OPEX) by leveraging virtualization and cloud technologies. NFV decouples the software implementation of network functions from the underlying hardware, and it provides an abstraction of network functions such as firewalls, deep packet inspectors, load balancers, among others, via software components that can run on general purpose devices that can be located in a variety of telecom infrastructure, including data centers, network nodes, and end-user facilities. These Virtual Network Functions (VNFs) can easily be created, moved or migrated from one equipment to another without the need to install new specialized hardware, allowing a faster deployment of the services and providing innovation and a great number of opportunities for the world of networked systems. In this paper is provided an overview of NFV, explaining its characteristics, enabling technologies, benefits, use cases and challenges, as well as its relationship with another emerging technology as Software Defined Networking (SDN). The architectural framework, several uses case and a list with 179 SDN/NFV open-source projects are also provided, at the end it is described the Proof of Concepts (PoCs) and some research lines in this interesting research area.
Full paper: http://ieeexplore.ieee.org/document/8247541/ or Here
SDN/NFV open-source projects: https://drive.google.com/file/d/0B5x07DW9JAXbektsOFo3STZMbGM/view
OpenStack Sydney: The talk describes the structure of most open source communities, governance, and how members of the community communicate. The talk describes the first 5 things that every newcomer to OpenStack should follow. Reviewing code is an important aspect of community participation and we describe how to do good code reviews.
Byobu is an easy-to-use wrapper around the tmux (or screen) terminal multiplexer. This means that it makes it easy for you to open multiple windows and run multiple commands within a single terminal connection.
The log file of the OpenStack Tacker is disabled by default. If we want to see the log, we should enable it. Following guide is executed in the DevStack environment:
The lock is placed when an apt process is running and is removed when the process completes. If there is a lock with no apparent process running, this may mean the process got stuck for some reason.
If a program stops working or responding, Windows 10 can automatically report the problem to Microsoft and check for a solution. By default, Windows 10 collects information that describes the problem. This is called a problem report. It can include the name of the program that has stopped working, the date and time when the problem occurred, and the version of the program that has encountered the problem. Sending a problem report allows Windows 10 to notify you if a solution is available. This is called “Error Reporting”. If you are not happy with the OS behavior, for example, because of privacy or disk space issues, high CPU processing, you might want to disable it.
Someone might attack your Linux based system. You can drop attacker IP using IPtables.
However, you can use the route or ip command to null route unwanted traffic. A null route (also called as blackhole route) is a network route or kernel routing table entry that goes nowhere. Matching packets are dropped (ignored) rather than forwarded, acting as a kind of very limited firewall. The act of using null routes is often called blackhole filtering.
You can null route (like some time ISP do prevent your network device from sending any data to a remote system) stopping various attacks coming from a single IP (read as spammers or hackers IP) using the following syntax on a Linux based system.