FreeSBC:Cloud:Virtmanager Installation A - Revision history

Luc Morissette: /* Accessing the FreeSBC-SW web portal */

2019-01-04T22:02:50Z

Accessing the FreeSBC-SW web portal

← Older revision		Revision as of 18:02, 4 January 2019
Line 92:		Line 92:
	More info on KVM NIC source mode here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-attch-nic-physdev		More info on KVM NIC source mode here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-attch-nic-physdev

	== Accessing the FreeSBC~~-SW~~ web portal ==		== Accessing the FreeSBC web portal ==
	# Open a web browser to the management IP of the FreeSBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358		# Open a web browser to the management IP of the FreeSBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358
	# You should get to the FreeSBC Configuration Wizard <br/> [[File:TSBC_WebPortal_Configuration_wizard.jpg\|350px]]		# You should get to the FreeSBC Configuration Wizard <br/> [[File:TSBC_WebPortal_Configuration_wizard.jpg\|350px]]

	From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration Guide]] to continue the installation.		From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration Guide]] to continue the installation.

Serdar Civici at 06:12, 26 December 2018

2018-12-26T06:12:39Z

← Older revision		Revision as of 02:12, 26 December 2018
Line 88:		Line 88:
	#Set the name of you VM : ie FreeSBC in this example. Make sure “Customized Hardware” checkbox is checked <br/> [[File:Virt_Manager_4.png\|400px]]<br/>		#Set the name of you VM : ie FreeSBC in this example. Make sure “Customized Hardware” checkbox is checked <br/> [[File:Virt_Manager_4.png\|400px]]<br/>
	#Add the desired number of Ethernet interfaces as macvtap in “passthrough” source mode, and select the device model you want to emulate (virtio vs e1000)<br/> [[File:Virt_Manager_5.png\|400px]]<br/>		#Add the desired number of Ethernet interfaces as macvtap in “passthrough” source mode, and select the device model you want to emulate (virtio vs e1000)<br/> [[File:Virt_Manager_5.png\|400px]]<br/>
			<br/>
			<br/>
			More info on KVM NIC source mode here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-attch-nic-physdev

	~~More info~~ on ~~KVM NIC source mode here~~: ~~https~~://~~access~~.~~redhat~~.~~com~~/~~documentation/en~~-~~us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-attch-nic-physdev~~		== Accessing the FreeSBC-SW web portal ==
			# Open a web browser to the management IP of the FreeSBC, on port 12358. Example if your server address is 192.168.178.30, the URL would be: <br/> http://192.168.178.30:12358
			# You should get to the FreeSBC Configuration Wizard <br/> [[File:TSBC_WebPortal_Configuration_wizard.jpg\|350px]]

			From here, you can go to [[TSBC-SW:WebPortal:Initial Configuration\|Web Portal Initial Configuration Guide]] to continue the installation.

Serdar Civici at 06:10, 26 December 2018

2018-12-26T06:10:14Z

← Older revision		Revision as of 02:10, 26 December 2018
Line 75:		Line 75:

	== Create VM for FreeSBC ==		== Create VM for FreeSBC ==
			Define the amount of CPUs and RAM according to requirements.
			Follow the VM creation process by dialog tabs as below

			#Launch virtmanager from the Linux GUI: Applications→System Tools→Virtual Machine Manager<br/>
			#Create new VM: File→New Virtual Machine
			#Import Existing disk Image,
			#*Click to Browse
			#*Select “LocalImages” repo and click the refresh button
			#*Select your the image you've juste copied, my_freesbc_3_0_107_3.qcow2 in this example, and click “Choose volume” <br/> [[File:Virt_Manager_1.png\|400px]]<br/>
			#Set OsType and Version to Linux/Centos7 and click "Forward" <br/> [[File:Virt_Manager_2.png\|400px]]<br/>
			#Select quantity of RAM and CPU and click "Forward" <br/> [[File:Virt_Manager_3.png\|400px]]<br/>
			#Set the name of you VM : ie FreeSBC in this example. Make sure “Customized Hardware” checkbox is checked <br/> [[File:Virt_Manager_4.png\|400px]]<br/>
			#Add the desired number of Ethernet interfaces as macvtap in “passthrough” source mode, and select the device model you want to emulate (virtio vs e1000)<br/> [[File:Virt_Manager_5.png\|400px]]<br/>

			More info on KVM NIC source mode here: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/virtualization_administration_guide/sect-attch-nic-physdev

Serdar Civici: /* Upload Image File to Proxmox cloud */

2018-12-26T05:48:50Z

Upload Image File to Proxmox cloud

← Older revision		Revision as of 01:48, 26 December 2018
Line 68:		Line 68:
	As a result, you should get file fresbc_kvm.qcow2. Please, mention "Product Key" and keep containing email in a safe place.		As a result, you should get file fresbc_kvm.qcow2. Please, mention "Product Key" and keep containing email in a safe place.

	== Upload Image File to ~~Proxmox cloud~~ ==		== Upload Image File to Server/Cloud ==
	You need an SFTP client to upload FreeSBC image to Proxmox. For example, using WinSCP SFTP Client. You need to uncompress FreeSBC image to the virtual images folder and rename the image to your vm name if you want. In our sample, we used /srv/LocalImages as a folder.		You need an SFTP client to upload FreeSBC image to Proxmox. For example, using WinSCP SFTP Client. You need to uncompress FreeSBC image to the virtual images folder and rename the image to your vm name if you want. In our sample, we used /srv/LocalImages as a folder.
	> cd /srv/LocalImages		> cd /srv/LocalImages

Serdar Civici: /* Upload Image File to Proxmox cloud */

2018-12-26T05:46:55Z

Upload Image File to Proxmox cloud

← Older revision		Revision as of 01:46, 26 December 2018
Line 69:		Line 69:

	== Upload Image File to Proxmox cloud ==		== Upload Image File to Proxmox cloud ==
	You need an SFTP client to upload FreeSBC image to Proxmox. For example, using WinSCP SFTP Client. You need to uncompress FreeSBC image to virtual images ~~folders~~. In our sample, we used /srv/LocalImages as a folder		You need an SFTP client to upload FreeSBC image to Proxmox. For example, using WinSCP SFTP Client. You need to uncompress FreeSBC image to the virtual images folder and rename the image to your vm name if you want. In our sample, we used /srv/LocalImages as a folder.
	> cd /srv/LocalImages		> cd /srv/LocalImages
	sudo tar xzvf freesbc_kvm_3.0.107.3_172_233929.qcow2.tar.gz		sudo tar xzvf freesbc_kvm_3.0.107.3_172_233929.qcow2.tar.gz
	sudo mv freesbc_kvm.qcow2 my_freesbc_3_0_107_3.qcow2		sudo mv freesbc_kvm.qcow2 my_freesbc_3_0_107_3.qcow2


	== Create VM for FreeSBC ==		== Create VM for FreeSBC ==

Serdar Civici at 05:45, 26 December 2018

2018-12-26T05:45:59Z

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:FreeSBC:Cloud:Virtmanager Installation}}
-Below is the procedure to work with an instance of TelcoBridges's virtual SBC on a virtmanager infrastructure.
+Below is the procedure to work with an instance of TelcoBridges's virtual SBC on a Virtmanager infrastructure.
 == Requirements ==
 Minimal Cloud requirements:
@@ Line 63: / Line 63: @@
 More details on HW/CPU/NIC requirements can be found here: [[FreeSBC:RequirementsMatrix|RequirementsMatrix]]

Serdar Civici at 05:41, 26 December 2018

2018-12-26T05:41:31Z

← Older revision		Revision as of 01:41, 26 December 2018
Line 1:		Line 1:
	~~aaaaa~~		{{DISPLAYTITLE:FreeSBC:Cloud:Virtmanager Installation}}

			Below is the procedure to work with an instance of TelcoBridges's virtual SBC on a virtmanager infrastructure.
			== Requirements ==
			Minimal Cloud requirements:
			* 64 bits infrastructures only
			* Virtio/e1000 NIC interface
			* One Ethernet adapter for management
			* One or more Ethernet adapter(s) for data
			{\| cellpadding="5" border="1" class="wikitable"
			\|-
			! width="150" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Sessions
			! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| CPU
			! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| RAM
			! width="100" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Disk Space
			! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" \| Ethernet ports
			\|-
			\| valign="top" \|
			Up to 5,000
			\| valign="top" \|
			2
			\| valign="top" \|
			4 Gb
			\| valign="top" \|
			40 Gb
			\| valign="top" \|
			1 Gbps
			\|-
			\| valign="top" \|
			5,000-20,000
			\| valign="top" \|
			4
			\| valign="top" \|
			8 Gb
			\| valign="top" \|
			60 Gb
			\| valign="top" \|
			4 X 1 Gbps or
			1 X 10 Gbps
			\|-
			\| valign="top" \|
			20,000-50,000
			\| valign="top" \|
			4**
			\| valign="top" \|
			16 Gb
			\| valign="top" \|
			80 Gb
			\| valign="top" \|
			1 X 10 Gbps
			\|-
			\| valign="top" \|
			Above 50,000
			\| valign="top" \|
			6**
			\| valign="top" \|
			24+ Gb
			\| valign="top" \|
			100 Gb
			\| valign="top" \|
			Multiple 10 Gbps
			\|}

			More details on HW/CPU/NIC requirements can be found here: [[FreeSBC:RequirementsMatrix\|RequirementsMatrix]]

Serdar Civici: Created page with "aaaaa"

2018-12-26T05:37:07Z

Created page with "aaaaa"

New page

aaaaa