[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Openshift origin high availability and best practices




----- Original Message -----
> From: "Jakob Praher" <jakob praher info>
> To: dev lists openshift redhat com
> Sent: Sunday, December 29, 2013 10:08:57 AM
> Subject: Openshift origin high availability and best practices
> 
> Hi,
> 
> I am currently using openshift origin (broker package is version
> 1.5.2 - is there a way get a version number other than rpm - I have
> many openshift packages w/ different versions, yet I installed it
> using puppet).

Package versions aren't significant, other than indicating which is newer. If you installed via puppet, you either got the latest from a "nightly" repo (most likely) or from a stable release (currently 3).

> 
> For fault tolerance, I am using:
> - two separate masters
> - glusterfs + external mysql to keep the data in sync
> 
> What about districts, are they already an alternative to multiple
> separate installations (http://brenton-leanhardt.rhcloud.com/?p=102)

No, they have nothing to do with HA or separate installations.

> Generally I would like to ask the list, if there is already a plan
> emerging for having high availability apps w/ the benefits that the
> out-of-the box cartridges are automating (creating a database
> instance, no need to keep uids in sync, ...). The greatest pain
> today is that I have to create every app twice and have to take that
> they share the same user ID (for NFS).

I understand why you'd want to do this, but in general you just cannot count on gear UIDs matching up. They are not meant to.

Shared storage is still a hard problem on OpenShift, at least if you want shared access to be confined to a particular set of gears.

> I saw that there was a blog post about master/slave database
> replication, is this cartridge also available in origin? Also I need
> to have the data tree in sync.
> (https://www.openshift.com/blogs/cloudy-with-a-chance-of-data-master-slave-database-replication-on-openshift)

We are exploring ways to scale replicated DB gears within an application to make them HA. It looks promising, but I have no idea when you'll see it in Origin. I'm sure someone has a proof-of-concept out on a branch on github somewhere.

For now, if you want your app's DB to be HA, the advice is still to manage that DB separately from OpenShift. You can configure connection parameters with app-specific env variables.

> Furthermore although changing the valid gear sizes to small,medium
> console only allows me to create small gears.

See:
 http://openshift.github.io/documentation/oo_administration_guide.html#set-default-gear-quotas-and-sizes
 http://openshift.github.io/documentation/oo_administration_guide.html#set-the-type-of-gears-a-specific-user-can-create 

> Best regards,
> Jakob
> 
> 
> 
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]