sureshanaparti commented on a change in pull request #226: URL: https://github.com/apache/cloudstack-documentation/pull/226#discussion_r710880200
########## File path: source/quickinstallationguide/qig.rst ########## @@ -611,121 +607,194 @@ to using the CloudStack UI for the actual configuration of our cloud. Configuration ------------- -As we noted before we will be using security groups to provide isolation and -by default that implies that we'll be using a flat layer-2 network. It also -means that the simplicity of our setup means that we can use the quick -installer. - - UI Access ~~~~~~~~~ To get access to CloudStack's web interface, merely point your browser to -http://172.16.10.2:8080/client The default username is 'admin', and the -default password is 'password'. You should see a splash screen that allows you -to choose several options for setting up CloudStack. You should choose the -Continue with Basic Setup option. +the IP address of your machine e.g. http://172.16.10.2:8080/client +The default username is 'admin', and the default password is 'password'. -You should now see a prompt requiring you to change the password for the admin -user. Please do so. +Setting up a Zone +----------------- +Zone Type +~~~~~~~~~ -Setting up a Zone -~~~~~~~~~~~~~~~~~ +A zone is the largest organization entity in CloudStack - and we'll be +creating one. + +.. warning:: + We will be configuring an Advanced Zone in a way that will allow us to access both + the "Management" network of the cloud as well as the "Public" network - we will do so + by using the same CIDR (but different part of it, i.e. different IP ranges) for both + "Management" (Pod) and "Public" networks - which is something your would NEVER do + in a production - this is done strictly for testing purposes only in this guide! + +Click "Continue with Installation" to continue - you will be offered to change your +root admin password - please do so, and click on OK. + +A new Zone wizard will pop-up. Please chose Advanced (don't tick the "Security Groups") and click on Next. + +Zone Details +~~~~~~~~~~~~ -A zone is the largest organization entity in CloudStack - and we'll be -creating one, this should be the screen that you see in front of you now. And -for us there are 5 pieces of information that we need. +On this page we enter where our dns servers are located. +CloudStack distinguishes between internal and public DNS. Internal DNS is +assumed to be capable of resolving internal-only hostnames, such as your +NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve +public IP addresses. You can enter the same DNS server for both types, but +if you do so, you must make sure that both internal and public IP addresses +can route to the DNS server. In our specific case we will not use any names +for resources internally, and we will indeed set them to look to the same +external resource so as to not add a namerserver setup to our list of +requirements. #. Name - we will set this to the ever-descriptive 'Zone1' for our cloud. -#. Public DNS 1 - we will set this to ``8.8.8.8`` for our cloud. +#. IPv4 DNS 1 - we will set this to ``8.8.8.8`` for our cloud. -#. Public DNS 2 - we will set this to ``8.8.4.4`` for our cloud. +#. IPV4 DNS 2 - we will set this to ``8.8.4.4`` for our cloud. #. Internal DNS1 - we will also set this to ``8.8.8.8`` for our cloud. -#. Internal DNS2 - we will also set this to ``8.8.4.4`` for our cloud. +#. Internal DNS2 - we will also set this to ``8.8.4.4`` for our cloud. -.. note:: - CloudStack distinguishes between internal and public DNS. Internal DNS is - assumed to be capable of resolving internal-only hostnames, such as your - NFS server’s DNS name. Public DNS is provided to the guest VMs to resolve - public IP addresses. You can enter the same DNS server for both types, but - if you do so, you must make sure that both internal and public IP addresses - can route to the DNS server. In our specific case we will not use any names - for resources internally, and we have indeed them set to look to the same - external resource so as to not add a namerserver setup to our list of - requirements. +#. Hypervisor - this will be the primary hypervisor used in this zone. In our + case, we will select KVM. + +Click "Next" to continue. + +Physical Network +~~~~~~~~~~~~~~~~ +There are various network isolation methods supported by Cloudstack. The +default VLAN option will be sufficient for our purposes. For improved +performance and/or security, Cloudstack allows different trafic types to run Review comment: ```suggestion performance and/or security, Cloudstack allows different traffic types to run ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
