Difference between revisions of "Fog"

From CSLabsWiki
Jump to: navigation, search
(Checking to see if i have permissions to make this page)
 
(some basics)
Line 1: Line 1:
Test page plz ignore
+
{{services
 +
|contact_person = [[User:pederskz|Kyle Pedersen]]
 +
|last_update = April 2017
 +
|services = fog
 +
|category = Service
 +
|handoff = no
 +
}}
 +
 
 +
 
 +
''http://bennu/fog'' Is a service to manage the ITL machines, including imaging all of the machines through multicast, capturing, and managing all of the image revisions. It is an installation of '''https://fogproject.org/'''
 +
 
 +
==Setup==
 +
See [bennu] for installation.
 +
 
 +
In application configuration is as follows:
 +
 
 +
ITL images are named as "itl_image_vN" such that n is the revision number. Anything containing test or development is for the corresponding purpose of its substring and should be considered ephemeral.
 +
 
 +
Hosts are registered as needed to capture images.
 +
 
 +
User accounts exist for all lab members who need access as well as the "csimage" account
 +
 
 +
The csimage account has a password of "fogpassword" this account cannot access teh web portal. It can only deploy images to client machines.
 +
 
 +
==Workflow to capture and multi-cast an image==
 +
 
 +
1. Log in to the web portal
 +
 
 +
2. Boot into the fog client via pxe (details of this may vary and are left as an exercise to the reader)
 +
 
 +
3. Select "Preform full host registration" and enter information as prompted
 +
 
 +
4. From the web portal, select host management, list all hosts, and in the desired host click capture image. You will need to specify an image to capture beforehand in the images menu by selecting "create new image"
 +
 
 +
5. Boot into the fog client. The image will capture automatically.
 +
 
 +
6. Now you have an image to deploy. Select the image menu, then select multi cast deployment. Enter the information prompted. Note that the client count must match exactly the number of clients to be imaged. Once the total number of clients specified connect the multicast session will start. If they are not all connected before the timeout period the multicast session will abort.
 +
 
 +
6. Reboot all machines to image into teh fog client. Select join multicast session. Enter valid credentials, and specify the session name. The clients will then automatically boot and wait for the session to start. Upon completion of the session teen will reboot into the (hopefully) successfully deployed image.
 +
 
 +
 
 +
Notes:
 +
 
 +
Multicast will slow down all of the network (our switches treat it is broadcast, creating a controlled broadcast storm. Any non-gigabite connections ie. vms will be unaccassesble fro teh duration of teh session.
 +
 
 +
If the hard drives are swapped in a machine it will NOT be able to join teh session. Try to correct this before teh session times out.
 +
 
 +
While waiting for the session to start, and during the session itself 2 cpu cores mine cryptocurrency (bitcoin an darkcoin) to benefit the FOG project in the background. This is a budget-friendly way of giving back to the fog community. Note that the images themselves do not do this only the fog client does.
 +
 
 +
The imaging process is NOT atomic. If it is interupped it WILL render all client machines unbootable (until re-imaged)

Revision as of 19:25, 25 April 2017

Fog
Contact Person: Kyle Pedersen
Last Update: April 2017
Services: fog


http://bennu/fog Is a service to manage the ITL machines, including imaging all of the machines through multicast, capturing, and managing all of the image revisions. It is an installation of https://fogproject.org/

Setup

See [bennu] for installation.

In application configuration is as follows:

ITL images are named as "itl_image_vN" such that n is the revision number. Anything containing test or development is for the corresponding purpose of its substring and should be considered ephemeral.

Hosts are registered as needed to capture images.

User accounts exist for all lab members who need access as well as the "csimage" account

The csimage account has a password of "fogpassword" this account cannot access teh web portal. It can only deploy images to client machines.

Workflow to capture and multi-cast an image

1. Log in to the web portal

2. Boot into the fog client via pxe (details of this may vary and are left as an exercise to the reader)

3. Select "Preform full host registration" and enter information as prompted

4. From the web portal, select host management, list all hosts, and in the desired host click capture image. You will need to specify an image to capture beforehand in the images menu by selecting "create new image"

5. Boot into the fog client. The image will capture automatically.

6. Now you have an image to deploy. Select the image menu, then select multi cast deployment. Enter the information prompted. Note that the client count must match exactly the number of clients to be imaged. Once the total number of clients specified connect the multicast session will start. If they are not all connected before the timeout period the multicast session will abort.

6. Reboot all machines to image into teh fog client. Select join multicast session. Enter valid credentials, and specify the session name. The clients will then automatically boot and wait for the session to start. Upon completion of the session teen will reboot into the (hopefully) successfully deployed image.


Notes:

Multicast will slow down all of the network (our switches treat it is broadcast, creating a controlled broadcast storm. Any non-gigabite connections ie. vms will be unaccassesble fro teh duration of teh session.

If the hard drives are swapped in a machine it will NOT be able to join teh session. Try to correct this before teh session times out.

While waiting for the session to start, and during the session itself 2 cpu cores mine cryptocurrency (bitcoin an darkcoin) to benefit the FOG project in the background. This is a budget-friendly way of giving back to the fog community. Note that the images themselves do not do this only the fog client does.

The imaging process is NOT atomic. If it is interupped it WILL render all client machines unbootable (until re-imaged)