官术网_书友最值得收藏!

Using templates with firewall and NAT settings

One of the major problems is that vApp templates do not keep their vApp router settings when they are templated and redeployed. Using templates with firewall and NAT settings is a way around it.

Getting ready

We need a vApp that has been configured with a vApp router and contains some firewall and NAT rules. You can use the vApp you created in the Forwarding an RDP (or SSH) session into an isolated vApp recipe in this chapter.

How to do it...

  1. Make sure the vApp that you want as a template is stopped.
  2. Right-click on the vApp and choose Copy to....
  3. Choose a new Name, OvCD, and a Storage Profile for the vApp:
  4. The vApp will now be copied.
  5. After the vApp is copied, you can deploy it. It is now a full copy, including the vApp router rules of the original vApp.

How it works...

It is not the most ideal way to do this, but it works. There are several downsides of this solution. One is that you will need these templates in each organization; you cannot use them centrally. The other one is that users would be able to delete, alter, or otherwise use these templates' VMs. You can use sharing to resolve this problem, but then you lose the user's ability to self provision.

For sharing, see the Sharing a vApp recipe in Chapter 3, Better vApps.

There's more...

Another solution for this problem is to use vCenter Orchestrator to deploy vApp router rules on demand. There are a lot of scripts out there, and I would recommend googling for them. In the following screenshot you can see the existing scripts in the vCenter Orchestrator (vCO) library:

主站蜘蛛池模板: 青铜峡市| 西林县| 当雄县| 玉龙| 湟源县| 九龙县| 泌阳县| 明光市| 洛扎县| 丰城市| 宜黄县| 南岸区| 安宁市| 同仁县| 抚宁县| 锡林浩特市| 中西区| 柳林县| 濉溪县| 阜新| 乌海市| 磐石市| 拜泉县| 昆明市| 额济纳旗| 威宁| 伊金霍洛旗| 简阳市| 通化市| 桃江县| 历史| 广德县| 兴宁市| 齐齐哈尔市| 新密市| 南涧| 深州市| 会同县| 全州县| 冷水江市| 广安市|