User:Henning Sprang/WorklogDevCampEssen2013-06
Contents
Worklog
Friday
- Organization stuff, get introduced / updated by the Hotel staff with the location and how to handle things
- set up the irc channel openstack-devcamp on oftc
- made an introduction round - we're a nice mixture of people from single freelancers over consultants in medium sized shops to superlarge companies and with very varying experiences, all very interesting, some total beginners with openstack some people working with it since 2 years
- Interesting: https://www.aoterra.de/
- Updated my devstack installation on my test server
- Which devstack bfranch to check out? master?
- for something stable, at the start, when we don't want to run in broken stuff it's stable/grizzly
Saturday
- Try tu run my old devstack install from last workshop...
Processing dependencies for python-quantumclient==2.2.2a1.8.g418fdf8 error: Installed distribution pyparsing 1.5.6 conflicts with requirement pyparsing==1.5.7
I've overheard somebody saying python lib install has changed to use virtualenv. So, there might be some thing that got scrambled, before fighting with old leftovers, I decide to simply start back from scratch. Reinstall my dedicated server, and get gogin again from scratch!
- use debian wheezy for this(that's my preferred base system for stable systems)? Nope, probably more devs are using ubuntu?
- no do ubuntu precision first
- ok, start again with ubuntu... but:
- instance doesn't start, there are vague errors on the dashboard, but I cannot find any logs... as with my first tries. logs are disabled by default...
- now looking for logfiles, again... but I see none, also no screen session as it should be the case... irc channel seems to be extremely crowded, at the same time extremely silent
- aqrgh - I didn't add the stack user to sudoers, and ran stack.sh as root - maybe the problem...
- unstack.sh seems to hang up the console where I started stack.sh - if I do "unstack.sh &" it keeps working!
- if I configure the log to be written into log/stack.sh, theres a symlink to the current logfile - but it only works if the logfile is directly in the devstack dir otherwise the symlink links to log/stack.log_TIMESTAMP which doesn't exist because relative to stack.log it's without the log/ ...
my localrc to load multiple images and have nice logs:
# some images to chose from IMAGE_URLS="${IMAGE_URLS:+${IMAGE_URLS},}http://download.grml.org/grml64-small_2012.05.iso" IMAGE_URLS="${IMAGE_URLS:+${IMAGE_URLS},}http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-uec.tar.gz" IMAGE_URLS="${IMAGE_URLS:+${IMAGE_URLS},}http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-amd64/current/images/netboot/mini.iso" IMAGE_URLS="${IMAGE_URLS:+${IMAGE_URLS},}http://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-amd64-disk1.img" # passwords DATABASE_PASSWORD=blablabla RABBIT_PASSWORD=blablabla SERVICE_TOKEN=blablabla SERVICE_PASSWORD=blablabla ADMIN_PASSWORD=blablabla # logging SCREEN_LOGDIR=$DEST/logs/screen SYSLOG=True LOGFILE=stack.sh.log
- Understood that you cannot just run an installer iso! The concept is different - you *need* to upload some kind of disk image into the system! that's all basically the same way as amazon aws works. Ubuntu has cloud images for this.
- if you use such an image, you cannot login ;) you must upload an ssh key, or create a keypair and download the created private key and use it. it is only added into newly created machines, not in existing ones!
TODO
- go through http://devstack.org/ again and my notes from previous workshop
- what's to do to get a running virtual machine?
- does it work well?
- Do I discover some bugs?
- Where are the logs?
- see if my patches for the iso loading from the last workshop are still necessary
- Checkout what would be to do to use openstack for virtualization management on a single rootserver for my personal convenience
- very important thing: I want a VPN for the control interface access!
- Figure out what's necessary to build a vagrant-openstack integration
- how does vagrant AWS work?
- What API does Openstack provide to do something similar?
Q and A
TODO: pull my notes from the last workshop here and add new questions popping up!
- A small single system production installation:
- is it a good idea, useful? It is useful if we want to create systems often, and maybe use existing amazon compatible tools.
- How to do it? Handmade? Use some distribuion like Rackspace / Mirantis / Crowbar?
- Which areas of OpenStack require development/testing/bugfixing/documentation work where I can help
- directly in OpenStack
- In packaging for Debian
Answered
- is it possible to resize an instance image somehow?
- snapshot and create it new with a different flavor!
- is it possible to add auth keys when the instance is already created?
- Same as resize: snapshot and create new!
More Ideas and Notes
Links
- Crazy - at mediawiki they wrote an openstack guy based on mediawiki :) http://www.mediawiki.org/wiki/Extension:OpenStackManager
- http://openstack.redhat.com/Main_Page
- https://wiki.ubuntu.com/ServerTeam/CloudArchive
- Rackspace stuff
- Crowbar stuff
- Main documentation http://www.openstack.org/software/start/
- IX Articles - I bought them
Further Work tasks
When there comes more time, there's a lot more interesting ideas to do:
- Current Work related stuff
- Figuring out the REST API
- Figuring out how to deploy Openstack Node and Virtual machines with Chef
- Checking out where and how Django and SQLAlchemy are used in OpenStack
- Might OpenStack or one of it's Distributions be more suited to setup self-service virtualization for developers than Proxmox.
- Checkout Openstack @Wikimedia - there was the idea to join the admin team there, see if that's still an option
- Getting an overview and start a comparision of OpenStack third party tools like
- Mirantis
- Rackspace OpenStack distribution
- HP Openstack distribution
- Do a comparison/ evaluation of Openstack against other virtualiztaion
management tools
- XCP
- OpenNebula
- Cloudstack
- Proxmox
- won't try. it's perl. there's 4 lines of comment in 1000 lines of code. However nice it will look like on the front, no way. There might be some good reasons why it isn't properly packaged and submitted to the debian and ubuntu archives, even though they have packages - sample: https://git.proxmox.com/?p=pve-common.git;a=blob;f=data/PVE/Tools.pm;h=0ec74d85d12ea216c162b5acbb999700a4e7f154;hb=HEAD
- Steps: define criteria and scenario, assess options against criteria, evaluate
- Figuring out how to compine ansible and openstack
- ansible config for an openstack server setup
- use ansible to deploy openstack virtual machines