[LON-CAPA-admin] Moving Winona server to Microsoft Azure

[Moore, Nathan T]

Thank for the detailed reply Stuart!

________________________________
From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> on behalf of Raeburn, Stuart <raeburn at msu.edu>
Sent: Saturday, August 11, 2018 10:20:56 AM
To: list about administration and system updating
Subject: Re: [LON-CAPA-admin] Moving Winona server to Microsoft Azure

Nathan,

>
> Do we need to set up a library and a student-access server, ie two separate machines?
>

LON-CAPA can be run on a single server/VM.

A library server must be able to host user (web) sessions, in any case, in order to support access to Authoring
Spaces for content creation.  In effect a library server is always both a library server and an access server.

In general I would recommend just installing a single server or VM when initially setting up a LON-CAPA domain.  You can then add access servers/VMs as needed, as LON-CAPA usage grows.  (You'll really only start to see the
benefits of using access servers/VMs to host student sessions if you have at least two access servers/VMs).

>
> Is it important to set up a redirect so that loncapa.winona.edu maps to the IP address above?  Should the
> redirect point to the library or student-access machine?
>

If you have a single LON-CAPA node for the winona domain, then loncapa.winona.edu should resolve to 23.99.228.207, and reverse DNS should be set so that the command: host 23.99.228.207 will report loncapa.winona.edu.

If you decide to deploy multiple LON-CAPA nodes in your domain, then you can configure one of the nodes to be a LON-CAPA load balancer node.  The load balancer node is the one which should be assigned to loncapa.winona.edu.  The load balancer can be a library server.  If you decide to do that, my recommendation would be to configure the LON-CAPA domain configuration for the winona domain so that users with author roles will have their sessions hosted on the load balancer/library server.

>
> What is necessary to move the winona domain and my problem files over to this new instance?
>

The directories you will need to move from the old (hosted) instance to the new locally installed instance are:  /home/httpd/lonUsers/winona and /home/httpd/html/priv/winona.

If any of your courses use content from other domains in the cross-institutional repository, you will need to have your node added to the authoritative list of LON-CAPA network nodes, maintained by the LON-CAPA Academic Consortium. Send e-mail to loncapa at loncapa.org to request membership of the network, if you have not done that previously, (see: loncapa.org/beforeyoustart.html for more information).


Stuart Raeburn
LON-CAPA Academic Consortium

________________________________________
From: LON-CAPA-admin <lon-capa-admin-bounces at mail.lon-capa.org> on behalf of Moore, Nathan T <nmoore at winona.edu>
Sent: Saturday, August 11, 2018 10:29 AM
To: lon-capa-admin at mail.lon-capa.org
Subject: {Disarmed} [LON-CAPA-admin] {Disarmed} Moving Winona server to Microsoft Azure

Hi all,


We plan to move the Winona loncapa server to a Linux virtual machine via Microsoft Azure services, see 23.99.228.207.

A few questions have come up with this transition - I apologize if I've missed them in the docs.


  1.
Do we need to set up a library and a student-access server, ie two separate machines?  My guess is yes.
  2.
is it important to set up a redirect so that loncapa.winona.edu maps to the IP address above?  Should the redirect point to the library or student-access machine?
  3.
What is necessary to move the winona domain and my problem files over to this new instance?

Any suggestions are appreciated!

Nathan Moore

Physics, Winona State University
Winona, MN, USA
_______________________________________________
LON-CAPA-admin mailing list
LON-CAPA-admin at mail.lon-capa.org
http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.lon-capa.org/pipermail/lon-capa-admin/attachments/20180811/f2e7d49c/attachment-0001.html>