CLOUDSTACK-4569 review comments on egress firewall and multiple ip per nic
Project: http://git-wip-us.apache.org/repos/asf/cloudstack/repo Commit: http://git-wip-us.apache.org/repos/asf/cloudstack/commit/5275618b Tree: http://git-wip-us.apache.org/repos/asf/cloudstack/tree/5275618b Diff: http://git-wip-us.apache.org/repos/asf/cloudstack/diff/5275618b Branch: refs/heads/disk-cache Commit: 5275618bcc94513f2e2d463adb878aa16628731f Parents: 7a0cd10 Author: radhikap <radhika.puthiyet...@citrix.com> Authored: Fri Aug 30 15:44:18 2013 +0530 Committer: radhikap <radhika.puthiyet...@citrix.com> Committed: Fri Aug 30 15:57:08 2013 +0530 ---------------------------------------------------------------------- docs/en-US/egress-firewall-rule.xml | 12 ++++++------ docs/en-US/multiple-ip-nic.xml | 6 +++--- 2 files changed, 9 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/5275618b/docs/en-US/egress-firewall-rule.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/egress-firewall-rule.xml b/docs/en-US/egress-firewall-rule.xml index 17bf15e..93d5a81 100644 --- a/docs/en-US/egress-firewall-rule.xml +++ b/docs/en-US/egress-firewall-rule.xml @@ -108,12 +108,12 @@ </orderedlist> </section> <section id="default-egress-policy"> - <title>Changing the Default Egress Policy</title> - <para>You can configure the default policy of egress firewall rules in Isolated Advanced - networks. Use the create network offering option to determine whether the default policy - should be block or allow all the traffic to the public network from a guest network. If no - policy is specified, by default all the traffic is allowed from the guest network that you - create by using this network offering.</para> + <title>Configuring the Default Egress Policy</title> + <para>The default egress policy for Isolated guest network is configured by using Network + offering. Use the create network offering option to determine whether the default policy + should be block or allow all the traffic to the public network from a guest network. Use this + network offering to create the network. If no policy is specified, by default all the traffic + is allowed from the guest network that you create by using this network offering.</para> <para>You have two options: Allow and Deny.</para> <formalpara> <title>Allow</title> http://git-wip-us.apache.org/repos/asf/cloudstack/blob/5275618b/docs/en-US/multiple-ip-nic.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/multiple-ip-nic.xml b/docs/en-US/multiple-ip-nic.xml index 790befc..344dc8d 100644 --- a/docs/en-US/multiple-ip-nic.xml +++ b/docs/en-US/multiple-ip-nic.xml @@ -75,9 +75,9 @@ </listitem> <listitem> <para>Click Acquire New Secondary IP, and click Yes in the confirmation dialog.</para> - <para>You need to specify the secondary IP address on the guest VM. &PRODUCT; will not - automatically configure the acquired IP address on the VM. Ensure that you assign IPs to - NIC each time the VM reboots.</para> + <para>You need to configure the IP on the guest VM NIC manually. &PRODUCT; will not + automatically configure the acquired IP address on the VM. Ensure that the IP address + configuration persist on VM reboot.</para> <para>Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in Port Forwarding or StaticNAT rules.</para> </listitem>
