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 かな。
012: We solve all of OpenStack's problems. YOU'RE WELCOME!
  • 012: We solve all of OpenStack's problems. YOU'RE WELCOME!
  • Brandon Whichard, Matt Ray, Coté
  • Software Defined Talk Podcast
Play
Summary

With the breaking news that Larry Ellison is stepping down from Oracle, we discuss Oracle’s potential and all the assets they acquired with Sun. We move onto the $40m funding round for Docker and what they could do with that money as they sort out how they’ll make money, and this leads to a discussion of OpenStack and how we’d “fix” it by becoming laser focused on developers (like Docker). After discussing “converged cloud” Matt Ray explains Minecraft which - turns out - is a thing.

With Brandon Whichard, Matt Ray, and Coté.

Sponsors: get $200 off when you register for 451’s Hosting and Cloud Transformation Summit (Oct 6th to 8th) when you use the code MC200 at 451events.com. Also, you should sign up for my newsetter at coteindustries.com/memo.

Subscribe to this podcast: http://feeds.feedburner.com/SoftwareDefinedTalk

Show notes
  • Larry steps down: “Mark Hurd and Safra Catz, currently co-presidents of Oracle, were both named CEO to replace Ellison, the company said today. Hurd will run sales, marketing and strategy, while Catz will remain chief financial officer and oversee legal and manufacturing operations. Ellison will become chairman, replacing Jeff Henley, and also take on the title of chief technology officer.”

  • Docker funding - a good blog post from them going over The Plan.

  • Rackspace not for sale

  • Cisco buys MetaCloud, the 451 analysis of the deal.
  • Is “converged cloud”/managed OpenStack private cloud” a thing? Cloud in a box?
  • We solve all of OpenStack’s problems. You’re welcome!
  • Microsoft buys Minecraft. Is that a thing?
  • “Minecraft has also not been adapted to take advantage of the graphical interface of Microsoft’s latest operating system” <- hah
  • "While Mr. Persson is said to accept that he may not stay for more than six months if a deal is struck"

  • Google Hangouts finally fails consistently enough, Matt Ray says that Zoom is the answer.

  • If you like video, see this episodes’ video recording.

Recommendations

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/

Watch on cliveboulton.com

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

AMD crea nube privada OpenStack , basada en el servidor SeaMicro SM15000

AMD crea nube privada OpenStack , basada en el servidor SeaMicro SM15000

AMD anunció una nueva colaboración con Canonical® que ofrece la manera más sencilla en la industria para crear una nube privada OpenStack®.  La solución consiste en el servidor SeaMicro SM15000™, Ubuntu® LTS 14.04 y OpenStack, que incluye un conjunto de potentes herramientas para crear una de las nubes privadas más flexibles y confiables. La colaboración entre AMD y Canonical elimina la…

View On WordPress

Vagrant と RDO で OpenStack をサクッと試す
構築や運用の面倒くささに定評のある OpenStack だけど、色々な所が出しているディストリビューションを活用することで、それを少しは軽減できる。 RDO は RedHat が出している OpenStack ディストリビューションのコミュニティ版だ。 今回はその RDO を Vagrant と組み合わせて OpenStack を触れる環境をサクッと作ってみる。 尚 Vagrant のバックエンドにはデフォルトの VirtualBox を使う。

今回使う Vagrantfile は以下の通り。 仮想マシンの上で仮想マシンを動かす (Nested Virtualization) ので、メモリは 4GB くらい欲しいところ。 ホストには CentOS 6.5 を使う。
$ cat << EOS > Vagrantfile
# -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = "2"

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.vm.box = "centos65"
  config.vm.network :private_network, ip: "192.168.33.10"
  config.vm.provider :virtualbox do |vb|
    vb.customize ["modifyvm", :id, "--memory", "4096", "--cpus", "2"]
  end
end

EOS

上記の Vagrantfile を元に VM を立ち上げてログインする。
$ vagrant up
$ vagrant ssh

まずは RDO をインストールする。
$ sudo yum install -y http://rdo.fedorapeople.org/rdo-release.rpm

これで OpenStack の動作に必要な各種 RPM のあるリポジトリが登録される。
$ rpm -ql rdo-release
/etc/pki/rpm-gpg/RPM-GPG-KEY-RDO-Havana
/etc/pki/rpm-gpg/RPM-GPG-KEY-foreman
/etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
/etc/yum.repos.d/foreman.repo
/etc/yum.repos.d/puppetlabs.repo
/etc/yum.repos.d/rdo-release.repo
$ cat /etc/yum.repos.d/rdo-release.repo
[openstack-havana]
name=OpenStack Havana Repository
baseurl=http://repos.fedorapeople.org/repos/openstack/openstack-havana/epel-6/
enabled=1
skip_if_unavailable=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-RDO-Havana
priority=98


次に Packstack をインストールする。 これは Puppet をベースにした OpenStack のインストーラだ。 上記のリポジトリから RPM をインストールしたり、その設定を行う。
$ sudo yum install -y openstack-packstack

Packstack を使って OpenStack をインストールする。 これにはかなり長い時間がかかるので気長に待つ。 今回の構成は、全てのコンポーネントを一つのホストにインストールする allinone にした。 同時に VirtualBox が NAT するプレフィックス (10.0.2.0/24) から Floating IP のレンジを切り出す。
$ packstack --allinone --provision-demo-floatrange=10.0.2.128/25

インストールが終わったら幾つか追加の設定を行う。 まずは、OpenStack の Web 画面 (コンポーネント名: Horizon) が、特定のアドレス (10.0.2.15) からのアクセスしか受け付けないようになっているので、その制限を外す。 このアドレスは VirtualBox が NAT しているものなので、直接アクセスすることはできないためだ。
$ sudo sed -i -e "s:^ALLOWED_HOSTS = .*$:ALLOWED_HOSTS = \['\*'\, ]:" /usr/share/openstack-dashboard/openstack_dashboard/local/local_settings.py
$ sudo service httpd restart

次にコンピューティング (コンポーネント名: Nova) 周りの設定を行う。 最初の設定は、ハイパーバイザのデフォルト設定が準仮想化の KVM になっているので、それを完全仮想化の qemu に変更している。 VirtualBox には VT パススルーの機能がないので KVM は動かないためだ。 二番目の設定は仮想マシンのキーボードを日本語に変更している。 三番目は仮想マシンの Web コンソールにアクセスするアドレスを到達性のあるものにしている。
$ sudo sed -i -e "s:^libvirt_type=.*$:libvirt_type=qemu:" /etc/nova/nova.conf
$ sudo sed -i -e "s:^#vnc_keymap=.*$:vnc_keymap=ja:" /etc/nova/nova.conf
$ sudo sed -i -e "s/10.0.2.15:6080/192.168.33.10:6080/" /etc/nova/nova.conf
$ sudo service openstack-nova-compute restart

さて、以下の URL にアクセスすれば OpenStack の Web 画面が閲覧できる。
http://192.168.33.10/dashboard

ログインに必要なアカウントは root ユーザのホームディレクトリにある。 デフォルトでは、一般ユーザ権限の demo と管理者権限の admin の二種類が用意されている。 以下の例では admin ユーザはパスワード 294332ec012e498c で、demo ユーザはパスワード 23927beaf78642e1 でログインできる。 デフォルトでパスワードは RDO が毎回ランダムに生成する。
$ sudo cat /root/keystonerc_demo
export OS_USERNAME=demo
export OS_TENANT_NAME=demo
export OS_PASSWORD=294332ec012e498c
export OS_AUTH_URL=http://10.0.2.15:35357/v2.0/
export PS1='[\u@\h \W(keystone_demo)]\$ '
$ sudo cat /root/keystonerc_admin
export OS_USERNAME=admin
export OS_TENANT_NAME=admin
export OS_PASSWORD=23927beaf78642e1
export OS_AUTH_URL=http://10.0.2.15:35357/v2.0/
export PS1='[\u@\h \W(keystone_admin)]\$ '

Web 画面から操作するのも良いけど、せっかくなので CUI のクライアントから VM インスタンスを作成してみよう。 まずは demo ユーザ用の環境変数を読み込む。
$ sudo -i
# source keystonerc_demo

まず VM のスペック (Flavor) を確認する。 一番小さいもの (m1.tiny) で十分だろう。
# nova flavor-list
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| ID | Name      | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+
| 1  | m1.tiny   | 512       | 1    | 0         |      | 1     | 1.0         | True      |
| 2  | m1.small  | 2048      | 20   | 0         |      | 1     | 1.0         | True      |
| 3  | m1.medium | 4096      | 40   | 0         |      | 2     | 1.0         | True      |
| 4  | m1.large  | 8192      | 80   | 0         |      | 4     | 1.0         | True      |
| 5  | m1.xlarge | 16384     | 160  | 0         |      | 8     | 1.0         | True      |
+----+-----------+-----------+------+-----------+------+-------+-------------+-----------+

次に接続するネットワークを確認する。 Neutron は OpenStack のネットワーク周りを管理するコンポーネントだ。 デフォルトで二つのネットワーク public と private ができている。 VM は private に接続する。
# neutron net-list
+--------------------------------------+---------+--------------------------------------------------+
| id                                   | name    | subnets                                          |
+--------------------------------------+---------+--------------------------------------------------+
| 3e33219e-4eaa-4246-82d9-3df0ad87fa80 | public  | c44ebd07-a74d-4f5c-88a1-8aabb68bcbc7             |
| 41002405-2da9-45c3-b2e0-7dd54a319815 | private | 9e44fe14-fed1-49ef-87f1-8ba9a05ccbb8 10.0.0.0/24 |
+--------------------------------------+---------+--------------------------------------------------+

VM の起動に使うイメージを確認する。 Glance は OpenStack のイメージファイルを管理するコンポーネントだ。 デフォルトで cirros という Linux ディストリビューションのイメージが登録されている。
# glance image-list
+--------------------------------------+--------+-------------+------------------+----------+--------+
| ID                                   | Name   | Disk Format | Container Format | Size     | Status |
+--------------------------------------+--------+-------------+------------------+----------+--------+
| ac256315-7aaa-4e9a-86a9-8c0c3a0bb5aa | cirros | qcow2       | bare             | 13147648 | active |
+--------------------------------------+--------+-------------+------------------+----------+--------+

ひと通り確認できたら VM インスタンスを起動する。
# nova boot --flavor 1 --image ac256315-7aaa-4e9a-86a9-8c0c3a0bb5aa --nic net-id=41002405-2da9-45c3-b2e0-7dd54a319815 vm1
+--------------------------------------+-----------------------------------------------+
| Property                             | Value                                         |
+--------------------------------------+-----------------------------------------------+
| OS-DCF:diskConfig                    | MANUAL                                        |
| OS-EXT-AZ:availability_zone          | nova                                          |
| OS-EXT-STS:power_state               | 0                                             |
| OS-EXT-STS:task_state                | scheduling                                    |
| OS-EXT-STS:vm_state                  | building                                      |
| OS-SRV-USG:launched_at               | -                                             |
| OS-SRV-USG:terminated_at             | -                                             |
| accessIPv4                           |                                               |
| accessIPv6                           |                                               |
| adminPass                            | AoSwqAFtGmK4                                  |
| config_drive                         |                                               |
| created                              | 2014-03-24T14:45:25Z                          |
| flavor                               | m1.tiny (1)                                   |
| hostId                               |                                               |
| id                                   | 9e829685-8bd9-4733-82b3-4f00d23c31dd          |
| image                                | cirros (ac256315-7aaa-4e9a-86a9-8c0c3a0bb5aa) |
| key_name                             | -                                             |
| metadata                             | {}                                            |
| name                                 | vm1                                           |
| os-extended-volumes:volumes_attached | []                                            |
| progress                             | 0                                             |
| security_groups                      | default                                       |
| status                               | BUILD                                         |
| tenant_id                            | 70791dac7fca40f1a432a1831dfdd58e              |
| updated                              | 2014-03-24T14:45:26Z                          |
| user_id                              | 610aad0d156841c3b9f497bb5496eed7              |
+--------------------------------------+-----------------------------------------------+

上手くいけば、これで VM インスタンスが追加されているはずだ。

ダッシュボードにログインする。

image



インスタンスタブに移動すると VM インスタンスが確認できるはず。

image



Web コンソールの画面に移動する。

image



VM インスタンスには cirros / cubswin:) でログインできる。

image



めでたしめでたし。

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

Watch on irq.tumblr.com

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

Metacloud, open stacks, fog computing, privacy, etc

*Well, it’s this or get eaten alive by the major Stacks and their colossal cloud-castles of Microsoft Azure, AWS and Google Cloud.

*If you don’t trust those three enormous entities, and if you suspect that they plan to use the Internet of Things to disrupt you and eat your lunch, this is where you are supposed to go instead.  Good luck with that.

http://newsroom.cisco.com/press-release-content?type=webcontent&articleId=1489587

PRESS RELEASE Cisco Announces Intent to Acquire Metacloud Acquisition of Private OpenStack Cloud Service Company Accelerates Cisco’s Intercloud Strategy

SAN JOSE, Calif. – September 17, 2014 – Cisco today announced its intent to acquire privately held Metacloud. Based in Pasadena, Calif., Metacloud deploys and operates private clouds  (((<—- nice term of art there, but Cisco is superb at that)))  for global organizations with a unique OpenStack-as-a-Service model that delivers and remotely operates production-ready private clouds (((<—- another one))) in a customer’s data center. 

Metacloud’s OpenStack-based cloud platform will accelerate Cisco’s strategy to build the world’s largest global Intercloud, (((<—- #3))) a network of clouds, ((( <—-#4)) together with key partners to address customer requirements for a globally distributed, highly secure cloud platform capable of meeting the robust demands of the Internet of Everything.  

Since announcing its Intercloud strategy in March, Cisco has made rapid progress, enlisting key technology partners, service and cloud providers, all of whom are standardizing upon the Cisco Cloud Services architecture, which is based on OpenStack open source software for building private and public clouds.  (((That wondrous sentence sums up the state of contemporary Internet of Things wrangling.  Eventually all this enlisting and standardizing is gonna lead to some more or less organized combat for more or less literal control of “Everything,” and God only knows what that looks like and how long it will last.)))

With OpenStack (((<—- that’s a good name, too)))  gaining global acceptance through its ability to handle any workload on any hypervisor  (((<—- on any what?)) )on any public or private cloud, the ability to manage OpenStack installations at scale is a critical component of Cisco’s Intercloud strategy.  Cisco’s acquisition of Metacloud’s remote managed OpenStack Private Cloud-as-a-Service platform will play an increasingly important role in accelerating Cisco customers’ journey to the cloud, enabling enterprises to match the as-a-Service operational benefits of public cloud with the security and control provided by private cloud. Metacloud also will allow service providers to combine their public cloud deployments with remotely managed OpenStack private clouds, and to deliver unique Intercloud offerings to their customers.

“Cloud computing has dramatically changed the IT landscape. To enable greater business agility and lower costs, organizations are shifting from an on-premise IT structure to hybrid IT – a mix of private cloud, public cloud, and on-premise applications,” said Hilton Romanski, senior vice president, Cisco Corporate Development. “The resulting silos present a challenge to IT administrators, as choice, visibility, data sovereignty  (((<—- Russians like this term “data sovereignty”)))  and protection in this world of many clouds requires an open platform. We believe Metacloud’s technology will play a critical role in enabling our customers to experience a seamless journey to a new world of many clouds, providing choice, flexibility, and data governance.”  (((In this context “data governance” means you are not a hapless, spied-upon pawn of Google, Microsoft or Amazon, but that’s a pretty weird adoption of the term “governance,” which commonly has something to do with a government rather than an entity like Google, Microsoft or Amazon.  But, well, if it’s the “Internet of Everything” that’s logically got to mean everything that current governments imagine they control.)))

Upon completion of the acquisition, Metacloud employees will join Cisco’s Cloud Infrastructure and Managed Services organization led by Faiyaz Shahpurwala, senior vice president. The acquisition of Metacloud is expected to be complete in the first quarter of fiscal year 2015, subject to customary closing conditions.

About Cisco

Cisco (NASDAQ: CSCO) is the worldwide leader in IT that helps companies seize the opportunities of tomorrow  (((<—- I’d stop right there if I were the copywriter here))) by proving that amazing things can happen when you connect the previously unconnected. For ongoing news, please go to http://thenetwork.cisco.com.

###

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. A listing of Cisco’s trademarks can be found at www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.

Forward-Looking Statements

This press release may be deemed to contain forward-looking statements, which are subject to the safe harbor provisions of the Private Securities Litigation Reform Act of 1995, including the expected completion of the acquisition and the time frame in which this will occur, the expected benefits to Cisco and its customers from completing the acquisition, plans regarding Metacloud personnel, and acceleration of Cisco’s Intercloud strategy. Readers are cautioned that these forward-looking statements are only predictions and may differ materially from actual future events or results due to a variety of factors, including, among other things, the potential impact on the business of Metacloud due to the uncertainty about the acquisition, the retention of employees of Metacloud and the ability of Cisco to successfully integrate Metacloud and to achieve expected benefits, business and economic conditions and growth trends in the networking industry, customer markets and various geographic regions, global economic conditions and uncertainties in the geopolitical environment and other risk factors set forth in Cisco’s most recent report on Form 10-K. Any forward-looking statements in this release are based on limited information currently available to Cisco, which is subject to change, and Cisco will not necessarily update the information.

 

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

Text
Photo
Quote
Link
Chat
Audio
Video