Bug 765354 (GLUSTER-3622)

Summary:	Required Ports Missing in AMI Licensing Documentation
Product:	[Community] Gluster-Documentation	Reporter:	Justin <justin>
Component:	Other	Assignee:	Divya <divya>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	bala, gluster-bugs, renee
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
URL:	http://download.gluster.com/pub/gluster/gluster-aws/3.2/3.2.0/Gluster_Virtual_Storage_Appliance_for_Amazon_Web_Services_3.2.0.pdf
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:	SF 2227
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Justin 2011-09-23 21:54:26 UTC

http://download.gluster.com/pub/gluster/gluster-aws/3.2/3.2.0/Gluster_Virtual_Storage_Appliance_for_Amazon_Web_Services_3.2.0.pdf 
Page 11, step 10 currently reads:

10. Select a security group with open TCP port number 22 in the Security Groups field, and click Continue.  A screen appears allowing you to review your settings.

We should also document other needed 111 (UDP), 24007 - 24*** (TCP), 38465 - 38*** (TCP) need to be opened otherwise there will be issues in the initial deploy (i.e. peer probe will fail, ).

Listed as Major, however, technically this is a blocker for AWS customers.  Please change severity as appropriate.

Comment 1 Balamurugan Arumugam 2011-10-10 06:03:18 UTC

In AWS, to launch more instances, its recommended to use gluster-ami-newinstance command in the master instance (where you did bootstrapping too) than launching with EC2 or EC2 console.

gluster-ami-newinstance launches instances and peer probe them.  We haven't seen any failure of peer probe or launching new instances in our testing/QA.

Can you tell me in what test case it fails and why we need to open these ports?

Comment 2 Justin 2011-10-10 18:05:03 UTC

Hi Bala,

The other day when I was testing the commands, each time I tried running the gluster-ami-newinstance command, the nodes didn't get probed and I noticed that it would wait several minutes for the node to power on, and would eventually time out (although they'd show powered ON in the web UI and could be shelled to).  At that point, the nodes wouldn't probe properly without having the ports in the security groups opened.

I was able to consistently recreate the problem that day, but now everything seems to be working fine (and works as documented).

Regards,

-Justin

Comment 3 Divya 2011-10-14 08:09:55 UTC

Closing this bug as it works as documented.