TimHas's profile - activity

2016-01-12 07:41:56 -0600 received badge  Popular Question (source)
2016-01-12 07:41:56 -0600 received badge  Famous Question (source)
2016-01-12 07:41:56 -0600 received badge  Notable Question (source)
2015-11-09 02:13:41 -0600 received badge  Popular Question (source)
2015-10-30 09:29:57 -0600 received badge  Enthusiast
2015-10-28 04:52:27 -0600 asked a question About the Cinder iSCSI traffic

Hey guys,

There is this little thing that I'm wondering about regarding the use of Cinder. The situation is: I have Cinder installed on my Controller Node and it assigns some memory for one of the VM's, and the Controller Node is connected to a SAN using an iSCSI connection. I would have set up a Storage Network in between the Controller and Compute Node. Now Cinder will take care of creating an iSCSI connection between the Compute Node and the SAN right?

Will all this iSCSI traffic go from the Compute Node straight to the SAN? Or will all the iSCSI traffic go from the Compute Node, throught the Controller (Storage) Node, to the SAN?

Thanks.

2015-10-22 09:08:54 -0600 asked a question Service Separation

Hey y'all,

I've been doing a lot of research on OpenStack lately. I'm trying to figure out what would be the best way to set up an OpenStack environment for my company. One of the first stepts would be to give advice about the hardware to buy. Currently we have 2 nodes. The specs of these nodes are:

  • 2x Intel Xeon CPU E5-2620 0 @2.00 GHz
  • 32 GB RAM
  • 600 GB HDD
  • 4 NIC

For now my company is thinking about setting up a cloud for maybe up to a hundred VMs. Later they might want to scale this up a lot. They want this cloud to be High Available, so I was thinking about a minimum of 6-8 nodes (2 controllers, 2 network nodes, 2 compute nodes + possibly nodes for Cinder/Swift storage).

Would this work for a setup that might have to scale out a lot? I've seen a couple of topologies where people would separate even more services, like separate Database or Load Balancer nodes for High-Availability. Sometimes they'd even set up 2 nodes for things like the Keystone or AMQP services.

So my question is: Would 6-8 nodes work for a HA-OpenStack environment that might have to scale out a lot later? And what is the best way to separate services on the nodes? As in, when do you put API's or the Database on a separate node or when do you put every service on a single controller node?

Thanks a bunch!

2015-10-22 09:08:53 -0600 asked a question Doesn't Swift use storage the same way Cinder does?

Hey guys,

I know Swift and Cinder store different kinds of data (Object vs Block), but I kind of imagened them both just using a bunch of HDDs/SSDs. I was looking at https://www.rdoproject.org/HA_Architecture (this RDO page) about High-Availability, and I noticed that there was a storage network with shared/distributed Storage. I thought this storage network would be for both Cinder and Swift, but the odd thing I noticed was that there were a couple of separate nodes for Swift, which where not connected to the Storage Network.

I'm currently working as an intern for this company and I'm trying to figure out how they could setup an OpenStack environment. The thing is that they have a SAN in their network and they want to use this for the storage of the Cinder and Swift services. So I kind of figured that we'd install Swift and Cinder on the same node and connect it to the management and storage network, and give it an iSCSI connection to the SAN.

This is why the separate Swift nodes, which are not connected to the storage network, threw me off. Is my idea for the setup not correct? Or is it just another way of doing things?