openstack

Happy Software Freedom Day! Find Out How NASA Has Contributed To Open Source Software:

“Back in 2008 and 2009, people were still trying to figure out what ‘cloud’ meant. While lots of people were calling themselves ‘cloud enabled’ or ‘cloud ready,’ there were few real commercial offerings. With so little clarity on the issue, there was an opportunity for us to help fill that vacuum.” - Raymond O’Brien, +NASA Ames Research Center 

Needing a way to standardize web space, a team of researchers at NASA Ames began a 2008 project known as NASA.net. The project offered a way to consolidate web development tools and data resources which heightened efficiency between all facets of the space agency. William Eshagh, another key contributor from NASA.net’s early days, aimed to find a way for web developers to upload code to a platform that was universally utilized.

“The basic idea was that the web developer would write their code and upload it to the website, and the website would take care of everything else,” according to Eshagh.

Still requiring an “infrastructure service” to manage the large quantities of data that NASA accumulates on a daily basis, the scope of the Ames project switched gears, and NASA.net was reorganized as Nebula. Rather than simply setting standards and providing a platform for web developers, the Nebula team would construct an open source compute controller. Early on, the collaborative nature of Nebula benefited development – as anyone with the understanding of the technology and desire could access the code and provide improvements. Raymond O'Brien, who remained on the Nebula team, reiterated the appeal of Nebula’s open source identity.

“From the beginning, we wanted this project to involve a very large community—private enterprises, academic institutions, research labs—that would take Nebula and bring it to the next level. It was a dream, a vision. It was that way from the start,” said O’Brien.

An early obstacle the pure open sourced project had to overcome was a piece of software known as the cloud controller, a pivotal segment of the project if the end users are to access computers or data. At this time, the existing tools were either written in the incorrect programming language or were closed source – not usable due to licensing limitations. However, It only took the Nebula team a matter of days to build a new cloud controller from scratch, and immediately began to attract interest from Rackspace Inc.

“We believed we were addressing a general problem that would have broad interest,” stated Eshagh. “As it turns out, that prediction couldn’t have been more accurate.”

Rackspace, known for providing open source storage, was set to begin construction of a similar cloud controller to what Nebula just released. Given the technical similarities between the two teams, Rackspace and Nebula began a partnership known as OpenStack – and a community of developers around the world would contribute towards the construction of what would become one of the most successful open source cloud operating systems.

The future of OpenStack, and other open source projects, are bright due the early efforts of the NASA.net team at Ames. Due to the initial devotion to keeping the project open source in those early days, a large majority of contributions to the OpenStack code came from community efforts outside of NASA. Today, on Software Freedom Day, be sure to checkout the following resources related to the OpenStack cloud, a NASA Spinoff.

Sources:
1. Web Solutions Inspire Cloud Computing Software
http://spinoff.nasa.gov/Spinoff2012/it_2.html
2. Nebula, NASA, and OpenStack
http://open.nasa.gov/blog/2012/06/04/nebula-nasa-and-openstack/
3. Software Freedom Day
http://softwarefreedomday.org/

Pythonista なら OpenStack プロジェクトが使っているパッケージは要チェック

プログラミングでベストプラクティスを見つけるには、他人のソースコードを読むのが手っ取り早いと思う。 特に、活動が活発な OSS は素晴らしい勉強材料になる。 その中でも OpenStack は世界中の Pythonista が寄ってたかって弄っているプロジェクトなので、なかなか良い感じ。 コンポーネント毎にちぐはぐ感はあっても間違いは少ないと思う。 そこで使われているパッケージを眺めているだけでも、結構な発見があるんじゃないかな。

とりあえず下準備としてディレクトリを一段掘ってソースコードをチェックアウトしておく。 OpenStack プロジェクトは本当にコンポーネントが多いので主要なものだけに絞った。

$ mkdir openstack
$ git clone https://github.com/openstack/nova.git openstack/nova
$ git clone https://github.com/openstack/neutron.git openstack/neutron
$ git clone https://github.com/openstack/horizon.git openstack/horizon
$ git clone https://github.com/openstack/keystone.git openstack/keystone
$ git clone https://github.com/openstack/glance.git openstack/glance
$ git clone https://github.com/openstack/cinder.git openstack/cinder
$ git clone https://github.com/openstack/swift.git openstack/swift

コンポーネントの動作に必要なパッケージは各プロジェクト直下にある requirements.txt に記述されている。 動作以外でテストに必要なものは test-requirements.txt にある。 ちなみに、これらはパッケージ管理システム PIP に読み取らせるためのフォーマットで書かれている。 pip install -r <requirements-file> みたいにして使えるわけ。

各コンポーネント毎に眺めるならこんな感じ。 ファイルにはパッケージのインストールに必要なバージョン情報とかコメントが入ってて邪魔なので取り除く。
$ cat openstack/nova/requirements.txt | cut -d ">" -f 1 | cut -d "=" -f 1 | cut -d "<" -f 1| sed -e "/^#/d" -e "/^$/d"
$ cat openstack/nova/test-requirements.txt | cut -d ">" -f 1 | cut -d "=" -f 1 | cut -d "<" -f 1| sed -e "/^#/d" -e "/^$/d"

個別に見ていっても良いけど、使っているパッケージを一覧したいのでシェルスクリプトを用意してみる。
$ cat openstack-unique-libs.sh
#!/bin/sh

LIBS=""
for i in `ls openstack`
do
  LIBS+=`cat openstack/$i/requirements.txt`
  LIBS+=`cat openstack/$i/test-requirements.txt`
done
echo "$LIBS" | cut -d ">" -f 1 | cut -d "=" -f 1 | cut -d "<" -f 1| sed -e "/^#/d" -e "/^$/d" | sort | uniq

実行してみる。
$ sh openstack-unique-libs.sh
-f http://pysendfile.googlecode.com/files/pysendfile-2.0.0.tar.gz
Babel
Django
Jinja2
MySQL-python
Paste
PasteDeploy
Routes
SQLAlchemy
WebOb
WebTest
alembic
amqplib
anyjson
argparse
boto
cliff
configobj
coverage
discover
django-nose
django_compressor
django_openstack_auth
docutils
dogpile.cache
eventlet
feedparser
fixtures
greenlet
hacking
hp3parclient
hplefthandclient
httplib2
iso8601
jsonrpclib
jsonschema
keyring
kombu
lesscpy
lockfile
lxml
mock
mox
netaddr
netifaces
nose
nose-exclude
nosehtmloutput
nosexcover
oauthlib
openstack.nose_plugin
ordereddict
oslo.config
oslo.messaging
oslo.rootwrap
oslo.sphinx
oslo.vmware
oslosphinx
oslosphinx# Horizon Core Requirements
oslosphinxpbr
oslotest
paramiko
passlib
pastedeploy
pbr
psutil
psycopg2
pyOpenSSL
pyasn1
pycadf
pycrypto
pylint
pymongo
pysendfile
pysqlite
python-ceilometerclient
python-cinderclient
python-glanceclient
python-heatclient
python-keystoneclient
python-ldap
python-memcached
python-neutronclient
python-novaclient
python-saharaclient
python-subunit
python-swiftclient
python-troveclient
pytz
qpid-python
requests
rtslib-fb
selenium
simplejson
six
sphinx
sqlalchemy-migrate
stevedore
suds
taskflow
testrepository
testscenarios
testtools
websockify
wsgiref
xattr

補足しておくと oslo.* は OpenStack プロジェクトが内製しているパッケージ。 あとは OpenStack のコンポーネント名が付くものも基本そうかな。

こういった活動が活発な OSS を幾つか知っておくと、良さげなライブラリへの感度は高まると思う。 ちなみに前述した「ちぐはぐ感」というのは、例えばあるコンポーネントは DB マイグレーションに alembic を使っているのに、別のコンポーネントでは sqlalchemy-migrate を使っている、とかそういうの。 上のリストを見ると他にはテストダブル用の mock と mox とかも、同様に被ってるよね。 ちなみに二つから選ぶなら、ぼくのオススメは alembic と mock かな。

An overview of the DevOps landscape these days, by the guys of Hashicorp. 

Two main approaches to infrastructure management have been arising in the last years

* a dynamic runtime configuration view, where you manage them with something like Puppet and you change dynamically the software you install and the configuration that you apply

* and a static configuration view, where you define and build your execution entities (eg, containers) and just let run.

Что посетить? День рождения OpenStack 22 июля!

В этом году OpenStack исполняется пять лет! Приглашаем Вас отпраздновать с нами это замечательное событие! 22 июля мы соберемся на площадке Cube завода Флакон (ул. Большая Новодмитровская 36, стр. 2). Начало в 11 часов утра. В программе: конференция, поздравления, подарки, фуршет, розыгрыш призов!

Регистрация

Clouds, open source, and new network models: Part 3

by James Urquhart  October 28, 2011

In part 1 of this series, I described what is becoming an increasingly ubiquitous model for cloud computing networks, namely the use of simple abstractions delivered by network systems of varying sophistication. In part 2, I then described OpenStack’s Quantum network service stack and how it reflected that model. Software defined networking (SDN) is an increasingly popular–but extremely nascent–model for network control, based on the idea that network traffic flow can be made programmable at scale, thus enabling new dynamic models for traffic management. Because it can create “virtual” networks in the form of custom traffic flows, it can be confusing to see how SDN and cloud network abstractions like Quantum’s are related.

http://news.cnet.com/8301-19413_3-20126245-240/clouds-open-source-and-new-network-models-part-3/

youtube

Scobleizer interviews Gluster CEO outside Facebook’s Palo Alto DC.

ithome.com.tw
雲端運算大革命 OpenStack具3大優勢快速發展
下個月將滿3歲的OpenStack雲端作業系統,在去年由OpenStack基金會主導後,繼續保持高速成長,目前已有超過190家廠商與相關組織加入,極有可能成為雲端時代的Linux,OpenStack內部包括了運算模組、網通模組和儲存模組,再搭配一個可以集中管理上述三大類模組的儀表板模組,最後組合而成一套OpenStack共享服務,並且可以提供虛擬機器的方式,對外提供運算資源以便彈性擴充或調度。簡單來說,OpenStack就是一套可以用來打造IaaS服務的開源雲端作業系統。
What is OpenStack? Part 2 of 2

Last Monday we looked at OpenStack in generic terms. Today we will look at it from Cisco’s perspective.

Overview

 Cisco helps customers build and operate OpenStack clouds with unified networking and next-generation cloud builder technology. 

Benefits of Cisco OpenStack

Faster Cloud Deployment

OpenStack reduces the time required to integrate and test cloud platform software components. Similarly, Cisco UCS Integrated Infrastructure simplifies the integration and deployment of the underlying hardware. Use Cisco’s group policy approach to further accelerate deployment though smart automation.

Scalable, High Performing Platforms

Cisco UCS and Nexus solutions provide industry-leading performance and Cisco architecture is simple and cost-effective to scale as demand rises.

Keep reading

vimeo

(via Piston Cloud Computing, Inc. | Easy. Secure. Open. » Watch: Arista Networks & Piston Cloud Webinar)

Internap Amplifies Cloud Play With $30 Million Voxel Acquisition

By Andrew R Hickey, CRN

January 03, 2012    10:20 AM ET

Cloud and IT infrastructure player Internap kicked off the new year Tuesday with the $30 million acquisition of Voxel Holdings, an enterprise cloud and hosting company that will fortify Internap’s push deeper into cloud computing. Adding Voxel, which was founded in 1999, to its cloud portfolio gives Internap a stronger foothold in the growing cloud market, an area Internap has already cut into with its OpenStack public cloud offering, an OpenStack storage offering, and its private cloud play. Based in New York, Voxel has locations that span North America, Amsterdam and Singapore and the company currently boasts 1,000 customers using its on-demand cloud and dedicated hosting services and its automated provisioning capabilities.

http://www.crn.com/news/cloud/232301171/internap-amplifies-cloud-play-with-30-million-voxel-acquisition.htm

클라우드 컴퓨팅, OpenStack 메모

OpenStack 커뮤니티가 private 클라우드의 성장을 방해하고 있다는 Matt Asay의 2015년 1월 20일 글

OpenStack 이론 vs. 현실

  • 만약 이론대로 현실에서도 적용되면 참 좋겠지만.
  • 현실에서의 OpenStack 은 여전히 엄청나게 복잡한 것으로 남아있다.
  • Cloudscaling의 Randy Bias 만큼 OpenStack 에 대해 아는 사람은 없을 것이다.
    • 그는 OpenStack 의 초기 개척자 중 한명이고, OpenStack Foundation 설립 멤버였다.
    • Bias가 “OpenStack 은 자기 자신의 무게를 못이겨 스스로 무너질 위험이 있다” 라고 경고하는 것 [1] 에 대해 OpenStack을 사용하는 사람들은 귀를 기울여야 한다.
    • Bias의 최근 글을 요약하면 [1]
    • OpenStack 은 커뮤니티 안에서 다양한 이해관계를 조화시키는 방법을 찾고 있지만, 정말로 필요한 것은 “제품 관리와 제품 전략 리더십” 이다.
  • 이러한 리더십이 없으면, 기업에서 OpenStack을 도입하려고 했던 David (Packet 의 인프라 조직장) 처럼, 기업이 클라우드에 기대하고 있는 편리함을 커뮤니티가 제공하기는 힘들다는 것을 배우게 될 것이다. [2]

한 달이 지나서 내가 읽은 대량의 문서들이 날짜가 지난 정보이거나 부정확하다는 것을 알게 되었다. 그래서 문서, 위키, irc, 커밋 메시지를 선별하면서 진실을 찾아야 했다. 기본이 된 이후에는, 많은 시간을 Python 디버깅에 썼다. “X는 동작하는가?” 를 증명하기 위해 오랜 시간 동안 디버깅을 해야 했고, 이것은 정말 느린 작업이었다. [2] - 우리가 OpenStack을 도입하기 위해 4개월 동안 한 작업을 쓰레기통에 던진 이유

VMware 의 최근 움직임

AT&T and OpenStack

AT&T is going to build a developer cloud using the OpenStack cloud framework. Before I go any further I should provide a quick explanation to OpenStack. OpenStack is an opensource cloud software created by mainly Rackspace and NASA, currently it is at release version 1.1. AT&T is hoping to release a cloud product called cloud architect. 

Source: http://arstechnica.com/business/news/2012/01/att-joins-openstack-as-it-launches-cloud-for-developers.ars