vkmc

# Install

> No handlers found for marconi.client (...)

This happens because the current user cannot create the log file (for the default configuration in /var/log/marconi/server.log). To solve it,
- Create the folder - sudo mkdir /var/log/marconi
- Create the file - sudo touch /var/log/marconi/server.log
- Run sudo marconi-server -v

# Messages

vkmc

Student:	Victoria Martínez de la Cruz
Mentor:	Alejandro Cabrera
Project:	Add a new storage backend to the OpenStack Message Queuing Service

vkmc

vkmc@havana:~$ virtualenv --distribute --python=python2.7 --no-site-packages marconi
Running virtualenv with interpreter /usr/bin/python2.7
The --no-site-packages flag is deprecated; it is now the default behavior.
New python executable in marconi/bin/python2.7
Also creating executable in marconi/bin/python
Installing distribute.............................................................................................................................................................................................done.
Installing pip...............done.

vkmc@havana:~$ source marconi/bin/activate

vkmc

## setting up

vkmc@havana:/opt/stack/marconi$ virtualenv marconi
New python executable in marconi/bin/python
Installing distribute..............................................................................................................................................................................................done.
Installing pip...............done.
vkmc@havana:/opt/stack/marconi$ source marconi/bin/activate
(marconi)vkmc@havana:/opt/stack/marconi$ python setup.py develop
running develop
running egg_info

vkmc

vkmc@havana:/opt/stack/marconi$ virtualenv marconi
New python executable in marconi/bin/python
Installing distribute.............................................................................................................................................................................................done.
Installing pip...............done.
vkmc@havana:/opt/stack/marconi$ source marconi/bin/activate
(marconi)vkmc@havana:/opt/stack/marconi$ python setup.py develop

Installed /tmp/easy_install-fWU_4I/pbr-0.5.16/d2to1-0.2.10-py2.7.egg
warning: no previously-included files found matching '.gitignore'
warning: no previously-included files found matching '.gitreview'

vkmc

#include <stdio.h>
#include <string.h>
#include <stdlib.h>
#include <sys/socket.h> // Linux socket interface
#include <arpa/inet.h> // ?
#include <netinet/in.h> // ?
#include <unistd.h>
#include <sys/types.h>
#include <regex.h>

vkmc

//DNS Query Program on Linux
//Author : Silver Moon ([email protected])
//Dated : 29/4/2009
 
//Header Files
#include<stdio.h> //printf
#include<string.h>    //strlen
#include<stdlib.h>    //malloc
#include<sys/socket.h>    //you know what this is for
#include<arpa/inet.h> //inet_addr , inet_ntoa , ntohs etc

vkmc

Every developer needs to have an work environment as close as possible to the real deployment to get to know the code, improve it and work on it creating new features. The more flexible the software in which you are working, there are more possibilities to consider.

Thus, after nearly three months of working on OpenStack, I found myself in the midst of an incredible mess of clouds of different versions, implemented in different ways across multiple operating systems.

After a while looking for solutions to organize my deployments and improve my productivity, I came across the concept of <em>cloud managers</em>. RightScale was one of the first to caught my attention and, as it provides support for OpenStack, I decided to see how it could fit my needs.

<!--more-->

<h4>Cloud details</h4>

vkmc

Floating IP listing

usage: quantum floatingip-list [-h] [-f {csv,table}] [-c COLUMN]
                               [--quote {all,minimal,none,nonnumeric}]
                               [--request-format {json,xml}] [-D] [-F FIELD]

List floating ips that belong to a given tenant.

optional arguments:
  -h, --help            show this help message and exit

vkmc

Cinder provides the list command to list all the volumes, but unluckily in this case we don't have
listing per tenant either.

[vkmc@thermalx2 devstack]$ cinder help list
usage: cinder list [--all-tenants [<0|1>]] [--display-name <display-name>]
                   [--status <status>]

List all the volumes.

Optional arguments: