There was an error in this gadget

Friday, May 27, 2011

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

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

Tuesday, May 24, 2011

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 with detailed step by step directions athttp://mirantis.blogspot.com/2011/05/openstack-deployment-on-fedora-using.html.

OpenStack Nova V.S. Eucalyptus Feature Comparison

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
(./)
{X}

OpenStack API (/ Rackspace API)
{X}
(./)

Secure communication
between components
(./)
{X}

Trivial horizontal
scalability for all
components
{X}
(./)

Built in web admin console
(./)
{X}

Command line interface for managing users
(./)
(./)


Friday, May 20, 2011

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 server team at Canonical.
Instead, Williamson said, Canonical sees clear technical advantages to OpenStack, specifically when focusing on ARM-based servers.
“We want to be sure Ubuntu can be in the forefront among server operating systems for ARM. We feel like we have an advantage there versus any of the established markets,” he said. “ARM’s Java support isn’t that solid yet, and Eucalyptus is written in Java. So that would have presented a problem for us. We’re also very focused on cloud deployment. For ARM, the virtualization technologies aren’t as mature there. With OpenStack, and the open development model, anyone can participate and contribute as they want, and really drive that functionality in their own self-interest. That is something we will contribute to and drive for our own self-interest. With Eucalyptus, there are some hurdles if we wanted to do that.”
Canonical has done this before, in the case of its support for KVM over Xen. In that case, the company took a risk in deciding to support what it believed was a superior virtualization hypervisor. That decision turned out OK, and there’s no reason to believe – as of yet – that its choice of OpenStack will hurt business.
Even so, Williamson admitted that he, and other Canonical executives, are nervous about whether OpenStack will be enterprise-ready in time for an expected September beta release of Ubuntu 11.10. Like any good gambler, Canonical is hedging its bet, planning to keep support for Eucalyptus through April 2015, and not ruling out a delay in its plan to make OpenStack the default.
“You never know. Come August, maybe we do need to switch it around. Both products are anticipated around the August, September timeline – there is some wiggle room there. … Talking to some of the other engineers, even Mark [Shuttleworth] himself, they were just as nervous, even more so, about this [decision],” Williamson said, comparing the OpenStack decision to the company’s choice of KVM.
Have you tried OpenStack and Eucalyptus? What are your impressions of the two technologies? Do you think this risk will pay off for Ubuntu?

Wednesday, May 11, 2011

Manage OpenStack with HybridFox

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

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 .

Monday, May 9, 2011

My thinking of Nova-network HA

There's simple map in my mind



Note: I forgot to draw a VIP for nova-network hosts public Virtual IP

Sunday, May 8, 2011

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

Thursday, May 5, 2011

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

How to implement [still thinking]
I hope someone can discuss with me .... there're two diagrams

Note Public network==Corporate network

My purpose 
goal1- Access instance from public network cloud users.
goal2- Using euca2ools to control openstack from cloud users host , so that API server should direct 
              connect public network.
goal3- 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.
goal4- High availability of all services , especially nova-api & nova-network.
goal5- Monitor NOVA hosts and instances.
goal6- Fast deployment

Tuesday, May 3, 2011

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

Multi Servers installation  

ubuntu
HOSTSNICNetworksIPgateway
ubuntu1eth0172.16.2.0/24172.16.2.79172.16.2.1
ubuntu1eth1192.168.1.0/24192.168.1.1192.168.1.2
ubuntu2eth0172.16.2.0/24172.16.2.78172.16.2.1
ubuntu2eth1192.168.1.0/24192.168.1.2none
ubuntu3~6eth1192.168.1.0/24192.168.1.3192.168.1.2

Match to this topology


Monday, May 2, 2011

Several Topologies

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 21 or 2





The working flow of running an instance in NOVA

Working Flow



1. User send running instance request to API server