Posts

Showing posts from May, 2011

[轉](Kernel-based Virtual Machine) + KQEMU

Image
Kernel-based Virtual Machine + KQEMU OpenStack is a cloud manage platform , not a hypervisor. 轉自 oSSLab 在 KVM(Kernel-based Virtual Machine) 裡面一直會談論到 QEMU 什麼是 QEMU 究竟在 KVM 的虛擬化中 QEMU 佔了什麼重要的地位. QEMU

Mirantis: OpenStack Deployment on Fedora using Kickstart

Wrote by Stephen Spector   May 18th, 2011  on  OpenStack Blog The team at Mirantis published a new blog post today on deploying OpenStack on Fedora ( http://mirantis.blogspot.com/2011/05/openstack-deployment-on-fedora-using.html ). From the blog: In this article, we discuss our approach to performing an Openstack installation on Fedora using our RPM repository and Kickstart. When we first started working with  OpenStack , we found that the most popular platform for deploying OpenStack was Ubuntu, which seemed like a viable option for us, as there are packages for it available, as well as plenty of documentation. However, our internal infrastructure is running on Fedora, so instead of migrating the full infrastructure to Ubuntu, we decided to make OpenStack Fedora-friendly. The challenge in using Fedora, however, is that there aren’t any packages, nor is there much documentation available. Details of how we worked around these limitations are discussed below. The complete blog post wit

OpenStack Nova V.S. Eucalyptus Feature Comparison

Image
This page attempts to enumerate how Nova and  Eucalyptus compare Current Status2011-05-23 The latest one click   OpenStack Compare In this topic , administrator should know about features in OpenStack NOVA   Feature Eucalyptus Nova EC2 Query API EC2 Soap API OpenStack API (/ Rackspace API) Secure communication between components Trivial horizontal scalability for all components Built in web admin console Command line interface for managing users

Ubuntu betting on OpenStack for cloud

In the world of open source cloud computing few topics have collected more attention recently than the ongoing development of OpenStack, the cloud computing project  launched by NASA and Rackspace . So, some people may not have been too surprised when Canonical said last week that OpenStack, and not Eucalyptus, would be Ubuntu’s future default cloud platform. However, Canonical’s decision to move away from Eucalyptus in favor of OpenStack could be risky. OpenStack is less than a year old and still very much in its infancy. Given all the publicity OpenStack has received, it might be fair to wonder whether Canonical was more concerned about being left behind than it was about the technology’s current efficacy. “A lot of folks figured it was a no brainer just because of the buzz. To be honest, that was not the only reason why we switched. If you switch to something just because it gets buzz, you’d be changing all the time,” said Robbie Williamson, the engineering manager for the Ubuntu s

Manage OpenStack with HybridFox

Image
HybridFox support OpenStack now Hybridfox  1.6 supports Openstack as well. But with pinch of salt. 1.6 Download Now

Deploy OPENSTACK with StackOps .....Testing

Deply Nova with StackOps [ENG]  StackOps Distro In my definition , It's a kind of SaaS. Help beginners to  deploy one or more private cloud. The assistant. 我會將他定義成一種SaaS服務,目前基本上用來協助佈署OpenStack 的私有雲。如果只需要擁有小規模的架構,這會是一個方便初期使用的好工具。 But, 目前的版本有兩個問題(two issues)

PREROUTING 169.254.169.254 ..Should not be set on ComputeNode & 500 internal error

Image
iptables rule for redirecting metadata request to API server on Nova-Compute node Effect : failed to SSH I believe that most of testers of OpenStack NOVA will face a problem with instance can ping but failed to SSH.Well , there r many possibilities .

My thinking of Nova-network HA

Image
There's simple map in my mind Note: I forgot to draw a VIP for nova-network hosts public Virtual IP

Who is StackOps

StackOps One of the interesting find in this conference was a tiny little company from Spain called  StackOps . If I have to describe StackOps in a simplistic way, I would say “StackOps is to OpenStack what Ubuntu was for Linux” . StackOps makes deploying OpenStack cloud seamless. Anyone can download the ISO image of the distribution from their website and have an OpenStack cloud running in 8-10 minutes. Keep an eye on this startup. They are going to play a critical role in taking OpenStack to more places than even Rackspace and other ecosystem partners http://www.cloudave.com/12145/openstack-conference-and-design-summit-a-recap/ OpenStack Conference And Design Summit: A Recap By  Krishnan Subramanian  on  May 6, 2011

Thinking about the possibility of these map......

Image
How to implement [ still thinking ] I hope someone can discuss with me .... there're two diagrams Note Public network==Corporate network My purpose   goal 1 - Access instance from public network cloud users. goal 2 - Using euca2ools to control openstack from cloud users host , so that API server should direct                connect public network. goal 3 - To avoid connection block of instance. In regular way , instance route from nova-network host.               Once nova-network dead , users will lose connection to instance. goal 4 - High availability of all services , especially nova-api & nova-network. goal 5 - Monitor NOVA hosts and instances. goal 6 - Fast deployment

[NOVA]Complete Installation of Multi Servers ---in detail

Multi Servers installation   ubuntu HOSTS NIC Networks IP gateway ubuntu1 eth0 172.16.2.0/24 172.16.2.79 172.16.2.1 ubuntu1 eth1 192.168.1.0/24 192.168.1.1 192.168.1.2 ubuntu2 eth0 172.16.2.0/24 172.16.2.78 172.16.2.1 ubuntu2 eth1 192.168.1.0/24 192.168.1.2 none ubuntu3~6 eth1 192.168.1.0/24 192.168.1.3 192.168.1.2 Match to this topology http://hugokuo-hugo.blogspot.com/2011/04/this-topology-works-fine-with-bzr-984.html

Several Topologies

Image
Topology 1-3 is been tested  1. Single Node , Network Combine with our corporate network All nova-component in one host , and the instance network is same as corporate network. Machine NICs Networks  1 1 or 2 1 or 2

The working flow of running an instance in NOVA

Image
Working Flow 1. User send running instance request to API server