[Openstack] hardware specifications for a little private cloud
Hi all, I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Alberto Molina Coballes IES Gonzalo Nazareno [1] http://www.referencearchitecture.org/hardware-specifications/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] hardware specifications for a little private cloud
Hello Alberto,I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other.Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-)What is the purpose of the lab ? Nuage Co - Razique Mahrouarazique.mahr...@gmail.com Le 26 mars 2012 à 12:56, Alberto Molina Coballes a écrit :Hi all,I'm a teacher at a sysadmin academy and we are planning to deploy aprivate cloud with OpenStack for educational/training purposes. We arecurrently selecting the optimal hardware configuration for our needsand I'm asking for some help to the list.Using [1] as a reference, we are clear about hardware specificationsof compute nodes (4 nodes with 2 processors), but we aren't about thebest solution for node controller and optimal storage:Option 1:1 server with 2 HD in RAID1 (nova controller, nova volume, glance,...) + 1 SAN iSCSIOption 2:1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...)We are excited about the possibilities that a private cloud brings tous and we don't want to fail in this critical step, so any help willbe really appreciated.Alberto Molina CoballesIES Gonzalo Nazareno[1] http://www.referencearchitecture.org/hardware-specifications/___Mailing list: https://launchpad.net/~openstackPost to : openstack@lists.launchpad.netUnsubscribe : https://launchpad.net/~openstackMore help : https://help.launchpad.net/ListHelp___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] hardware specifications for a little private cloud
2012/3/26 Razique Mahroua razique.mahr...@gmail.com Hello Alberto, I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other. Yes I know, but we have budget limitations. OpenStack HA is not an objective at this moment, it is a educational environment and we can still use a whiteboard ;) Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-) OK, but we are always considering 1 controller node and 4 compute nodes, the main doubt is regarding storage, is it better in controller node or in a external SAN iSCSI in a little cloud like this? What is the purpose of the lab ? Sysadmin training. At this moment, each student uses an isolated virtual LAN with Xen/KVM and shares some physical servers, but with a private cloud we can deploy a plethora of new configurations. Furthermore, the cloud itself. Alberto Molina Coballes IES Gonzalo Nazareno ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] hardware specifications for a little private cloud
One other thing you'll want to consider upfront w.r.t a hardware purchase is whether or not you want to support live migration. http://docs.openstack.org/cactus/openstack-compute/admin/content/configuring-live-migrations.html For this you'll need a large amount of shared storage (usually via NFS) where the instance files will live. Whether you choose SAN, NAS, or just a node with a bunch of disk is likely dependent on your environment and budget. Everett On Mon, Mar 26, 2012 at 5:17 AM, Razique Mahroua razique.mahr...@gmail.comwrote: Hello Alberto, I would advise you to deploy as much as node as you can, and dedicate separate services. That would bring you the possibility to extend your knowledge on HA mechanisms, and really understand how services interact each other. Let's say you spawn an instance from the api server, while it's is launched on a compute node - which is one another server. By having splitted architecture, you won't miss the obvious ;-) What is the purpose of the lab ? *Nuage Co - Razique Mahroua** * razique.mahr...@gmail.com Le 26 mars 2012 à 12:56, Alberto Molina Coballes a écrit : Hi all, I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Alberto Molina Coballes IES Gonzalo Nazareno [1] http://www.referencearchitecture.org/hardware-specifications/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] hardware specifications for a little private cloud
On 03/26/2012 06:56 AM, Alberto Molina Coballes wrote: Hi all, Hi Alberto! Welcome to the OpenStack community :) I'm a teacher at a sysadmin academy and we are planning to deploy a private cloud with OpenStack for educational/training purposes. We are currently selecting the optimal hardware configuration for our needs and I'm asking for some help to the list. Cool, sounds good. Using [1] as a reference, we are clear about hardware specifications of compute nodes (4 nodes with 2 processors), but we aren't about the best solution for node controller and optimal storage: Option 1: 1 server with 2 HD in RAID1 (nova controller, nova volume, glance, ...) + 1 SAN iSCSI Option 2: 1 server with 12 HD in RAID5/6 (nova controller, nova volume, glance, ...) We are excited about the possibilities that a private cloud brings to us and we don't want to fail in this critical step, so any help will be really appreciated. Option 1 might be easier to set up and work with. Not sure about costs, though... For small setups like this, you might want to use the Filesystem Glance storage driver targeted at the local filesystem and use the SAN+isci for the volume operations only. This would make it a bit easier to diagnose issues and administer Glance. Also, don't forget about MySQL, RabbitMQ and keystone. You need to put those on the controller node too! :) Best, -jay ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
