Lack Of Ability To Have Ip Networks In Ebiz Provisioning Tool
(Doc ID 2429724.1)
Last updated on MAY 17, 2019
Applies to:EBS on Oracle Cloud: Provisioning and Administration - Version 12.2.6 to 12.2.8 [Release 12.2]
Information in this document applies to any platform.
On 12.2.6 version, Infrastructure
Lack of ability to have Ip networks in Ebiz Provisioning Tool
The current EBS orchestration on Oracle public cloud attach an internal network and an external NATED IP to each of the instances provisioned on the
OPC. This deployment may not suit to every customer as every virtual machine is sort of exposed to an external network and not desirable. We can restrict
the services on a port by port basis, but then Elastic IP are metered and is a cost to the company. There are also only limited IPV4 addresses. So why to
attach a NATIP when it is not required.
The default architecture should be that the NAT IP is only required for the Load Balancer entry point and also potentially for the orchestration VM that
is required by the EBS admin to ssh into and run the provisioning flows. All the other VMs including EBS application tier and the DB tier can be in an
internal network. It can be a custom network defined by the customer that suits to their deployment or something that we enforce depending on what is
supported by the OPC.
It is not just that EBS need to shift. Also need to make sure the services we depend on also has the VCN/SDN supported.
Expect to have the ability to have Ip networks in Ebiz Provisioning Tool.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document