PDA

View Full Version : SLES 12 Clustering



carnold6
25-Jan-2016, 17:03
SLES12 physical server with apache 2.4, 2 Xen VM's and a webapp called alfresco. We are getting ready to update to SP1 and after that, i have been tasked with clustering the SLES12 server. We will use server 2012 R2 hyper-v for the SLES12 SP1 nodes. Since we do not have any support contract, it looks like we have to "make" the HA extension from disc 2 of the installation media, right? Can anyone provide a doc or pointers on how exactly to do this?

smflood
26-Jan-2016, 11:38
On 25/01/2016 16:04, carnold6 wrote:

> SLES12 physical server with apache 2.4, 2 Xen VM's and a webapp called
> alfresco. We are getting ready to update to SP1 and after that, i have
> been tasked with clustering the SLES12 server. We will use server 2012
> R2 hyper-v for the SLES12 SP1 nodes. Since we do not have any support
> contract, it looks like we have to "make" the HA extension from disc 2
> of the installation media, right? Can anyone provide a doc or pointers
> on how exactly to do this?

The High Availability Extension is a chargeable module available
separately and with it's own media - for SLES12 SP1 see
https://download.suse.com/Download?buildid=GARdbigjMhI~

I don't believe there's enough on DVD2 of SLES12 SP1 to build and use
clustering.

HTH.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

carnold6
26-Jan-2016, 17:01
On 25/01/2016 16:04, carnold6 wrote:

> SLES12 physical server with apache 2.4, 2 Xen VM's and a webapp called
> alfresco. We are getting ready to update to SP1 and after that, i have
> been tasked with clustering the SLES12 server. We will use server 2012
> R2 hyper-v for the SLES12 SP1 nodes. Since we do not have any support
> contract, it looks like we have to "make" the HA extension from disc 2
> of the installation media, right? Can anyone provide a doc or pointers
> on how exactly to do this?

The High Availability Extension is a chargeable module available
separately and with it's own media - for SLES12 SP1 see
https://download.suse.com/Download?buildid=GARdbigjMhI~

I don't believe there's enough on DVD2 of SLES12 SP1 to build and use
clustering.

I must say, i do NOT like the SLES12 licensing model!!! 1 of the reasons we haven't renewed our support. While not as convoluted as MS licensing, it certainly seems to going down that road.

smflood
26-Jan-2016, 18:26
On 26/01/2016 16:04, carnold6 wrote:

> I must say, i do NOT like the SLES12 licensing model!!! 1 of the reasons
> we haven't renewed our support. While not as convoluted as MS licensing,
> it certainly seems to going down that road.

Umm this isn't new with SLES12 as the High Availability Extension has
always been a chargeable extra for SLES (the term "module" was
introduced with SLES12). Of course uou are free to add/build cluster (or
any) software yourself to SLES but then you won't be supported by SUSE
thus negating the enterprise nature of SLES.

I also don't believe SUSE are alone in charging extra for some of their
additional modules/extensions offering extra services.

HTH.
--
Simon
SUSE Knowledge Partner

------------------------------------------------------------------------
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------

carnold6
26-Jan-2016, 19:11
On 26/01/2016 16:04, carnold6 wrote:

> I must say, i do NOT like the SLES12 licensing model!!! 1 of the reasons
> we haven't renewed our support. While not as convoluted as MS licensing,
> it certainly seems to going down that road.

Umm this isn't new with SLES12 as the High Availability Extension has
always been a chargeable extra for SLES (the term "module" was
introduced with SLES12). Of course uou are free to add/build cluster (or
any) software yourself to SLES but then you won't be supported by SUSE
thus negating the enterprise nature of SLES.

I also don't believe SUSE are alone in charging extra for some of their
additional modules/extensions offering extra services.

I don't want to turn this into a *****ing thread, thats not what i am trying to do. I am not saying SLES/SuSE should not charge for modules and add-ons because they should. What i am saying is this whole registration code SCC thing is convoluted and doesn't always work like it should. The following is probably the most frustrating: use to be, you could get RPM's like apache, PHPx and other stuff off the install media that you can no longer do. We don't have a fat budget and we find as we grow, our server also needs to grow. Its just frustrating! We have used SuSE since mid 90's. We like the stability, ease of use and want to keep using SuSE products. I will finish this by saying, i dont like where SuSE/SLES is going......

Now, back to the issue: i attained the 60 day trial download and reg code. Adding the iso using add-on in yast. It asks for the reg code and i enter the code but will not take it. I login to our SCC and do not see the HA subscription there. See, this doesn't always work like it is suppose to.......... So how do i need to get this working if i can't get the code added in SCC?

Then i face our SLES12 (no SP1) server: this server will be updated to SP1 sometime this week but even then we face the reg code issue with SP1 and the HA extension! So let me ask you, how would you handle this situation with little to no budget?

carnold6
26-Jan-2016, 23:25
So before i go any further, let me make sure clustering will do what we need done. The existing SLES12 (serverA) server runs apache 2.4 with many web sites and does proxypass/reverse with some SSL, Xen with 2 VM's and a webapp called alfresco. We are not so much worried about the Xen VM's right now as we are apache and the webapp. We would like to cluster this existing server with another SLES12 server so that when apache service or webapp fail, it fails over to the 2nd node. Can this be done?