On 4 December 2014 at 07:59, phuc vandinh <phucvd...@gmail.com> wrote: > Hi everyone, > I'm a Sys Admin. and Now, my App Dev Team request me to use Docker into > Openstack for DevOps Enviroment. > But via Openstack Hypervisor Matrix, I saw that Docker miss some Openstack > feature-supported. It is not support Cinder,.. > I want to use KVM to be fully supported with the other Openstack products > as: Neutron, Cinder,... > > What is the best way to use Docker into Openstack in this case? and How? > I should use Docker like as hypervisor via Nova Driver > or > there is one way that I can deploy Docker on top of OpenStack + KVM and They > still warrant performance and have some advance features of Docker? > > -- > Thanks && Best Regards! > > Philip
Hi Philip! What about this: --- root@openstack-1:~$ apt-cache show nova-compute-flex .... Description-en: Openstack Compute - Ubuntu Flex container support OpenStack is a reliable cloud infrastructure. Its mission is to produce the ubiquitous cloud computing platform that will meet the needs of public and private cloud providers regardless of size, by being simple to implement and massively scalable. . OpenStack Compute, codenamed Nova, is a cloud computing fabric controller. In addition to its "native" API (the OpenStack API), it also supports the Amazon EC2 API. . Nova is intended to be modular and easy to extend and adapt. It supports many different hypervisors (KVM and Xen to name a few), different database backends (SQLite, MySQL, and PostgreSQL, for instance), different types of user databases (LDAP or SQL), etc. . This package provides common dependencies and setup for the Ubuntu Flex based container hypervisor, providing a secure way to run instances as LXC containers under OpenStack. --- Info: http://www.ubuntu.com/cloud/tools/lxd AFAIK, Docker isn't a VM, so, it makes no sense to use it as a "regular hypervisor" under Nova. I did not tried it via Heat. And trying to use Docker within a regular VM, like when using CoreOS, it also makes no sense (for me), mostly because Docker (or the containers) bring to you, a real baremetal-cloud, so, again, it makes no sense to use it within a virtualized Instance. Also, each Docker/Container needs 1 IP, so, when with CoreOS, I have no idea about how to manage this without using creepy NAT tables and tons of Port Forwards... I'm sure you'll enjoy 1 IPv6 address for each container, by far, much simpler, no NAT, no Port Forwards, easy to manage with native OpenStack Security Groups. Just my two bitcents... :-) Best! Thiago
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
